You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b728e19
Browse filesBrowse the repository at this point in the historyBrowse files
fix(semantics): a join condition reads only the items its engine lets it see
An ON condition was checked against every FROM item of its level. In
PostgreSQL it sees only its own comma group, up to the join: `a, b JOIN
c ON a.id = c.id` is an "invalid reference to FROM-clause entry", also
from a subquery or a parenthesised join, and an ON condition reading a
later comma group or a later item of its own join chain is a "missing
FROM-clause entry". DuckDB lets it read every earlier item and rejects
only later ones. A new dialect rule, join_conditions_read, gives each
join condition the items it reaches: its own group on PostgreSQL, every
earlier item on DuckDB, and every item elsewhere, as before. The
existing name checks then report E222 or E201.
0 commit comments