Allow table_schema comparisons#6887
Merged
harshit-gangal merged 1 commit intovitessio:masterfrom Oct 16, 2020
Merged
Conversation
systay
force-pushed
the
6881fwd
branch
2 times, most recently
from
afb2e8a to
214c290
Compare
Signed-off-by: Andres Taylor <andres@planetscale.com>
harshit-gangal
approved these changes
Oct 16, 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.
If we encounter a
table_schemacomparison in a information_schema query, we'll just not rewrite it when we cant evaluate the expression on vtgateThis is a cherry-pick of #6881