add returning support in MERGE queries.
#1171
Draft
+148
−11
Conversation
This file contains 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
igalklebanov
added
api
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
igalklebanov
force-pushed
the
pg-merge-returning
branch
from
6c67c82
to
6f5bd45
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hey 👋
closes #1169.
As of PostgreSQL 17,
MERGEqueries now havereturningclause support.returning/returningAlltoMERGE.MultiTableReturningInterface, enforce it acrossDeleteQueryBuilder,UpdateQueryBuilderandMERGEbuilders. Why? the existingReturningInterfacedoesn't have thereturningAll(tables)methods, andINSERTqueries are the only ones that don't supportreturning table.*.merge_action()in a type-safe and aliasable way.