Open
Conversation
apstndb
force-pushed
the
feature/nested-update
branch
from
8d56cd7 to
3620b3f
Compare
Contributor
Author
|
I am doubting there is ambiousity between insert columns and paren query input |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR implements nested update.
This PR depends on Support DMLs with named schema #262, so I plans to rebase after it merged.Conflict is resolved.Note:
Columnsin nestedUPDATEis optional, soparseDMLInternal()andparseUpdate()have argumentnested bool.Breaking Changes
UpdateItemis now interface.Related Issue