Spanner: Session to database transaction-usage #4510
Merged
Conversation
This file contains hidden or 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
googlebot
added
the
cla: yes
Contributor
Author
|
Must have closed the wrong one. |
tseaver
approved these changes
Dec 4, 2017
Contributor
tseaver
left a comment
tseaver
left a comment
There was a problem hiding this comment.
We might want to ditch usage docs for individual transactions altogether: the Spanner team would prefer that everyone use database.run_in_transation, I believe.
Contributor
Author
|
So do I still merge this or just delete the file? |
Contributor
|
Merge it. I was just speculating that the whole chapter might be unwanted (by the Spanner team). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
No description provided.