Fix Field to SQL convert when materialized field is available #1080
Conversation
This file contains 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
mvorisek
force-pushed
the
fix_1078_inner_field_table_alias
branch
from
0f08d79
to
168073e
Compare
mvorisek
force-pushed
the
fix_1078_inner_field_table_alias
branch
from
58e57ed
to
6b97485
Compare
mvorisek
force-pushed
the
fix_1078_inner_field_table_alias
branch
from
6b97485
to
173ec13
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fix #1078
if we can reason materialized Field, it should be always used, it improves performance and fixes issues when the source table was aliased in SQL