add support for RETURNING clause (PostgreSQL, SQLite) - #310
Open
andreypopp wants to merge 1 commit into
Open
Conversation
INSERT/UPDATE/DELETE accept a trailing RETURNING clause. When the number of returned rows is statically known the single-row variants are used: single-tuple INSERT ... VALUES and INSERT ... SET map to select_one, ON CONFLICT DO NOTHING makes it select_one_maybe. The feature is dialect-checked (PostgreSQL, SQLite; -no-check=returning downgrades to a warning). RETURNING and conflict clauses on INSERTs with inferred columns (INSERT INTO t VALUES / SET with nothing following) are rejected, since the generated tuple is appended textually at the end of the statement (previously an inferred INSERT with ON CONFLICT silently produced invalid SQL). This is a limitation of the SQL codegen which can be lifted in the future. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
INSERT/UPDATE/DELETE accept a trailing RETURNING clause.
When the number of returned rows is statically known the single-row
variants are used: single-tuple INSERT ... VALUES and INSERT ... SET
map to select_one, ON CONFLICT DO NOTHING makes it select_one_maybe.
The feature is dialect-checked (PostgreSQL, SQLite; -no-check=returning
downgrades to a warning).
RETURNING and conflict clauses on INSERTs with inferred columns (INSERT
INTO t VALUES / SET with nothing following) are rejected, since the
generated tuple is appended textually at the end of the statement
(previously an inferred INSERT with ON CONFLICT silently produced
invalid SQL). This is a limitation of the SQL codegen which can be
lifted in the future.
Co-Authored-By: Claude Fable 5 noreply@anthropic.com