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
According to SQL:1999, it shouldn't be possible to write:
INSERT INTO tbl (a, b, c) DEFAULT VALUES ...;
Since UPSERT/REPLACE is syntactic sugar over a variant of INSERT .. ON CONFLICT ..., then I assume that one should also not be able to write:
UPSERT INTO tbl (a, b, c) DEFAULT VALUES ...;
The INSERT RFC and UPSERT/REPLACE RFC's EBNFs, as written, allow for this. The RFCs don't go into details about what this means with the insert column list when using DEFAULT VALUES -- therefore, it looks like a bug.
johnedquinn
changed the title
RFC-0030 DEFAULT VALUES with <insert columns list> bug
RFC-0030 and RFC-0011 DEFAULT VALUES with <insert columns list> bug
Dec 6, 2024
According to SQL:1999, it shouldn't be possible to write:
Since
UPSERT/REPLACE
is syntactic sugar over a variant ofINSERT .. ON CONFLICT ...
, then I assume that one should also not be able to write:The INSERT RFC and UPSERT/REPLACE RFC's EBNFs, as written, allow for this. The RFCs don't go into details about what this means with the insert column list when using DEFAULT VALUES -- therefore, it looks like a bug.
The EBNF should probably follow SQL:1999's more closely. See partiql/partiql-lang-kotlin#1666.
The text was updated successfully, but these errors were encountered: