Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Azure SQL Server sequential transaction execution #1537

Closed
shubham1172 opened this issue Feb 28, 2022 · 1 comment · Fixed by #1542
Closed

Azure SQL Server sequential transaction execution #1537

shubham1172 opened this issue Feb 28, 2022 · 1 comment · Fixed by #1542
Assignees
@shubham1172
Labels
kind/bug Something isn't working
Milestone
v1.7

Comments

@shubham1172
Copy link
Member

Description

Per #1505, the state store was updated the respect the order of transactions by skipping items that are not needed. This causes mechanisms like triggers to fail, if the operations are skipped. The proposal to fix the bug is by executing all the operations in the same order as specified.

Release Note

RELEASE NOTE: FIX Azure SQL Server state store's transaction API to execute all transactions sequentially.
@shubham1172 shubham1172 added the kind/bug Something isn't working label Feb 28, 2022
@shubham1172
Copy link
Member Author

/assign

@shubham1172 shubham1172 mentioned this issue Feb 28, 2022
Merged
1 task
@berndverst berndverst added this to the v1.7 milestone Mar 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shubham1172 shubham1172

Labels
kind/bug Something isn't working
Projects
None yet
Milestone
v1.7
Development

Successfully merging a pull request may close this issue.

Azure SQL Server: Update transaction API to execute sequentially shubham1172/components-contrib
2 participants
@berndverst @shubham1172