🐛 Bug ❓: Variable name collision for SQL cells using same table name in different schemas

[EED85]

Description

When using multiple SQL cells in marimo with DuckDB, creating tables with the same name in different schemas leads to a variable redefinition error.

Although the tables are fully qualified and valid in DuckDB, marimo raises an error due to internal variable name collisions.

---

Minimal Reproducible Example

-- Cell 1
CREATE TABLE finance.datalake.xx (id INT);

-- Cell 2
CREATE TABLE finance.information_layer.xx (id INT);

ERROR

This cell wasn't run because it has errors
This cell redefines variables from other cells.

'xx' was also defined by:

dl
Fix: Wrap in a function
Why can't I redefine variables?

Expected Behavior

Since the tables are created in different schemas, both statements should execute without conflict:

Environment

requires-python = ">=3.13"
dependencies = [
    "duckdb",
    "ipykernel>=7.2.0",
    "marimo>=0.23.8",
    "pandas>=3.0.3",
    "plotly>=6.7.0",
    "polars>=1.41.2",
    "pyarrow>=24.0.0",
    "pydantic-ai>=1.104.0",
    "ruff>=0.15.15",
    "sqlglot<30",
    "tabulate>=0.10.0",
]

That is my opinion. What is the marimo way, to handle this?

Best
Eric

[EED85]

My personal workarround:

-- SQL Cell 1
CREATE TABLE finance.datalake.xx (id INT);

-- SQL Cell 2
CREATE TABLE finance.information_layer.xx_fix (id INT);

Use duckdb conn in a python cell, so i can have same named tables in a different schemas.

conn.sql("""
    CREATE OR REPLACE TABLE finance.information_layer.xx(ID INT);
""")

[Light2Dark]

This looks like a bug with our sql ast parsing. Thanks for reporting.

[EED85]

Hi @Light2Dark ,

thanks for the answer.

How do you proceed here? Closing this thread and opening an issue instead?

[Light2Dark]

It's been fixed. #9744, will be out in the next release.

I'll close this discussion, thank you!