-
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
Add specific opting out of RETURNING/OUTPUT clause #29916
Labels
area-sqlite
area-sqlserver
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
customer-reported
type-enhancement
Milestone
Comments
roji
added
regression
type-bug
area-sqlserver
area-sqlite
and removed
type-enhancement
labels
Dec 22, 2022
This was referenced Dec 22, 2022
roji
added a commit
to roji/efcore
that referenced
this issue
Dec 22, 2022
roji
added a commit
to roji/efcore
that referenced
this issue
Jan 10, 2023
roji
added a commit
to roji/efcore
that referenced
this issue
Jan 10, 2023
roji
added a commit
to roji/efcore
that referenced
this issue
Jan 20, 2023
roji
added a commit
to roji/efcore
that referenced
this issue
Jan 25, 2023
ghost
pushed a commit
that referenced
this issue
Jan 26, 2023
This was referenced Feb 3, 2023
Closed
ajcvickers
added
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
and removed
Servicing-consider
labels
Feb 23, 2023
roji
changed the title
Configuration to opt out of occasionally problematic SaveChanges optimizations
Add specific opting out of RETURNING/OUTPUT clause
Oct 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-sqlite
area-sqlserver
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
customer-reported
type-enhancement
EF 7.0 changed the default update SQL to use the SQL RETURNING/OUTPUT for fetching back database-generated columns. Some cases where identified where this does not work, and so the following opt-out strategies were done:
However, various other incompatibility scenarios were gradually discovered - virtual tables and certain triggers types on SQLite. It's also not a good solution on SQL Server to tell users to configure a fake trigger if they have a problematic computed column.
As a result, in 8.0 we're adding UseSqlOutputClause for SQL Server and UseSqlReturningClause for SQLite, which are targeted, explicit opt-outs specifically for disabling these clauses. A user convention can be used to apply this to all entity types.
The text was updated successfully, but these errors were encountered: