Java: Update dbscheme for ParExpr removal.#2659
Merged
yo-h merged 5 commits intogithub:masterfrom Jan 28, 2020
Merged
Conversation
aschackmull
added
depends on internal PR
Contributor
Author
|
Note, that the test is expected to fail on this PR as it only makes sense in the context of the internal PR. |
aschackmull
force-pushed
the
java/remove-parexpr
branch
from
35565af to
0b3c90b
Compare
Contributor
Author
|
Rebased in order to solve submodule conflict. |
yo-h
approved these changes
Jan 28, 2020
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
2 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.
This is the dbscheme change corresponding to the extractor change to move parentheses out of the AST. We'll also need some changes to the QL libs, but these can come in a separate PR once the extractor changes are merged.