| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
It makes me queasy to think about reusing a batch or a transaction. If somebody wanted to examine the _commit_request after commit, that would be fine, but I don't see a case for resetting it. |
Sorry, something went wrong.
This is towards googleapis#1288 in preparation for the upgrade to `v1beta3`. In particular, a single `Mutation` protobuf instance in `v1beta3` is not sufficient to contain all changes to be committed, so we use the container that is up one level in the hierarchy.
|
OK. Should I file an issue to move the tombstone behavior into Batch? Also, would it be better to use the passed in commit_request after moving that behavior or should I do it in this PR? PS I just rebased, had a merge issue. |
Sorry, something went wrong.
|
I think we could just open an issue and go on. |
Sorry, something went wrong.
|
LGTY to merge? |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
Using protobuf CommitRequest in datastore Connection.commit.
| Back | FazBrowse Home | New Git URL |
This is towards #1288 in preparation for the upgrade to v1beta3. In particular, a single Mutation protobuf instance in v1beta3 is not sufficient to contain all changes to be committed, so we use the container that is up one level in the hierarchy.