ambiguous-column¶
Default severity: error
What it does¶
Reports an unqualified column that more than one table of the query has.
[tool.sqlty]
schema = "schema.sql"
[tool.sqlty.rules]
ambiguous-column = "warn"
schema.sql:
CREATE TABLE users (id INTEGER, name TEXT);
CREATE TABLE orders (id INTEGER, user_id INTEGER);
from sqlty import SQL
# error: [ambiguous-column] "column reference `id` is ambiguous"
q = SQL[tuple[int]]("--sql\nSELECT id FROM users u JOIN orders o ON o.user_id = u.id")
Open in playgroundWhy is this bad?¶
The database rejects the query. sqlty types the column from the first table that has it, so the annotation can look right while the query fails.
How to fix¶
Qualify the column: u.id. A column merged by USING (id) or any column of a NATURAL join is single and not reported; a subquery's own tables shadow the outer query. To accept one case, put # sqlty: ignore[ambiguous-column] on its line.
Configuration¶
An error by default: the database rejects such SQL. Lower or turn it off:
[tool.sqlty.rules]
ambiguous-column = "warn"
Only checked when a schema with tables is configured. Applies to the postgres, mysql and sqlite dialects.