better with_alias handling, including proper flattening when the expression accessed a single table #730
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.
Partially fixes:
This PR changes the handling of aliases, specifically, a dot-less with_alias("name") now figures out which table(s) it originates from. If its a single table, it acts as if
.with_alias("table.name")
was provided, adding itself to the detected tables dictionary.This is still incompatible with older versions for more complex queries, as can be seen with the second commit, how it fixes the subselect unittests. Specifically, due to a blank alias still getting a inferred table, queries which access multiple tables won't have their aliases at the "root" level of the Row nesting.
The behavior for dotted
.with_alias("table.name")
is the same as before.The behavior for non-expression "AS" is restored to pre-16c9395 state, with it just putting the parsed aliased at the root of the row besides, of course, inside _extras
Script which i used to test various cases, far more than the unittests