fix: support duckdb 1.1.0, update globals() for scanning (#2279)

* fix: support duckdb 1.1.0, update globals() for scanning

* clear when adding back originals

* unused

* minor edits

* don't modify globals; just exec with the correct globals

---------

Co-authored-by: Akshay Agrawal <akshay@marimo.io>

marimo/_sql/sql.py

@@ -8,6 +8,10 @@
 from marimo._output.rich_help import mddoc
 from marimo._plugins.ui._impl import table
 from marimo._runtime import output
+from marimo._runtime.context.types import (
+    ContextNotInitializedError,
+    get_context,
+)
 
 
 def get_default_result_limit() -> Optional[int]:
@@ -37,7 +41,22 @@ def sql(
 
     import duckdb  # type: ignore[import-not-found,import-untyped,unused-ignore] # noqa: E501
 
-    relation = duckdb.sql(query=query)
+    # In Python globals() are scoped to modules; since this function
+    # is in a different module than user code, globals() doesn't return
+    # the kernel globals, it just returns this module's global namespace.
+    #
+    # However, duckdb needs access to the kernel's globals. For this reason,
+    # we manually exec duckdb and provide it with the kernel's globals.
+    try:
+        ctx = get_context()
+    except ContextNotInitializedError:
+        relation = duckdb.sql(query=query)
+    else:
+        relation = eval(
+            "duckdb.sql(query=query)",
+            ctx.globals,
+            {"query": query, "duckdb": duckdb},
+        )
 
     if not relation:
         return None

pyproject.toml

@@ -85,7 +85,7 @@ dev = [
     # For server testing
     "httpx~=0.27.0",
     # For SQL
-    "duckdb~=1.0.0",
+    "duckdb~=1.1.0",
     # For testing mo.ui.chart, dataframes, tables
     "pandas>=1.5.3",
     "pandas-stubs>=1.5.3.230321",