Adds upsert entity operations using ON CONFLICT#428
Open
Conversation
Added variations of the `insert*` entity operations that use `ON CONFLICT <target> DO UPDATE` clauses to update values that conflict due to a constraint violation.
qxjit
reviewed
Feb 9, 2026
Member
qxjit
left a comment
qxjit
left a comment
There was a problem hiding this comment.
I think this is a great addition to the API. I think we should consider what the shape of the Expr.ConflictTargetExpr should be at the EntityOperation layer of the interface. In particular, I'd like it to be very straightforward for a new user to do an upsert by primary key without worrying about the the Expr API.
telser
reviewed
Feb 10, 2026
| Expr.ConflictTargetExpr -> | ||
| NEL.NonEmpty writeEntity -> | ||
| m [readEntity] | ||
| upsertAndReturnEntities tableDef target = do |
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
3 participants
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.
Added variations of the
insert*entity operations that useON CONFLICT <target> DO UPDATEclauses to update values that conflict due to a constraint violation.