* Skipped explicit Rollback of transaction on errors (server-side a…
#1230
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
asmyasnikov
added
bug
summaryBase version: v3.67.2-0.20240517192714-e3f2b5d853e4 (master) |
|
🌋 Here are results of SLO test for Native ydb-go-sdk/v3 over table-service: |
|
🌋 Here are results of SLO test for Go SDK gorm: |
|
🌋 Here are results of SLO test for Go SDK database/sql: |
|
🌋 Here are results of SLO test for Go SDK xorm: |
asmyasnikov
force-pushed
the
skip-rollback
branch
from
a7bd1b8 to
006f25a
Compare
…utomatically rolled back transactions on errors)
|
🌋 Here are results of SLO test for Native ydb-go-sdk/v3 over query-service: |
asmyasnikov
force-pushed
the
skip-rollback
branch
from
006f25a to
aac8216
Compare
asmyasnikov
commented
May 17, 2024
asmyasnikov
commented
May 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…utomatically rolled back transactions on errors)
Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Other information