-
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
Rolling back a bulk insert command doesn't work #28712
Labels
area-save-changes
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-bug
Milestone
Comments
roji
added a commit
to roji/efcore
that referenced
this issue
Aug 15, 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
Aug 15, 2022
roji
added a commit
to roji/efcore
that referenced
this issue
Aug 15, 2022
roji
added a commit
to roji/efcore
that referenced
this issue
Aug 15, 2022
roji
added a commit
to roji/efcore
that referenced
this issue
Aug 15, 2022
ghost
pushed a commit
that referenced
this issue
Aug 15, 2022
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-save-changes
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-bug
When a command is added to a batch which goes over a limit (e.g. too many commands, too many parameters), we "roll it back", resetting the batch's state as if that command wasn't added. When adding a bulk-insert command for SQL Server, this isn't done properly: the command is removed from the SQL Server pending commands list, but the base rollback tasks are skipped. As a result, the batch state partially remains as if the command has been successfully added.
The text was updated successfully, but these errors were encountered: