fix: returning all columns with "on conflict do update" #7534
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.
When using returning clauses in conjunction with
on conflicted do updatemust be considered as ScanUpdate.What did this pull request do?
This should fix #7538
User Case Description
When using
CreateInBatcheswithReturning{}in conjunction withON CONFLICTED DO UPDATE, it will either crash with panic, or run successfully without updating the object.The test will fails on both cases.
Panic example:
This PR add the
RETURNINGwithON CONFLICTED DO UPDATEas ScanUpdate.