-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use RETURNING/OUTPUT clause for UPDATE/DELETE #27547
Closed
Labels
area-perf
area-save-changes
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-enhancement
Milestone
Comments
8 tasks
roji
changed the title
Use RETURNING/OUTPUT clause for UPDATE
Use RETURNING/OUTPUT clause for UPDATE/DELETE
Mar 5, 2022
4 tasks
roji
added a commit
to roji/efcore
that referenced
this issue
Mar 17, 2022
roji
added
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
Mar 17, 2022
roji
added a commit
to roji/efcore
that referenced
this issue
Mar 17, 2022
roji
added a commit
that referenced
this issue
Mar 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-perf
area-save-changes
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-enhancement
When modifying a row that has database-generated values, we currently use UPDATE+SELECT:
We could use the RETURNING clause (SQL Server OUTPUT) to reduce this to one statement, like we're doing for INSERT in #27372. This would also allow removing the transaction.
For SQL Server with triggers, we would keep the above.
The text was updated successfully, but these errors were encountered: