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

[QS] Use implicit transaction for multi-statement queries #3423

Open
spuchin opened this issue Apr 3, 2024 · 0 comments · Fixed by #3882
Open

[QS] Use implicit transaction for multi-statement queries #3423

spuchin opened this issue Apr 3, 2024 · 0 comments · Fixed by #3882
Assignees
@VPolka
Labels
area/queryprocessor Query processor issues and requests

Comments

@spuchin
Copy link
Collaborator

spuchin commented Apr 3, 2024

When no explicit transaction is specified (empty TxControl and no BEGIN/COMMIT) we should use implicit transaction for the entire query.

SELECT ... FROM table1;
SELECT ... FROM table2;

Such query should be executed in single transaction.
@spuchin spuchin added the area/queryprocessor Query processor issues and requests label Apr 3, 2024
@spuchin spuchin mentioned this issue Apr 3, 2024
Open
@VPolka VPolka linked a pull request May 30, 2024 that will close this issue
implicit transaction in per statement mode #3882
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@VPolka VPolka

Labels
area/queryprocessor Query processor issues and requests
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

implicit transaction in per statement mode VPolka/ydb
2 participants
@spuchin @VPolka