New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix join alias resolution #2733
Conversation
71513f2
to
4760f03
Compare
Codecov Report
@@ Coverage Diff @@
## master #2733 +/- ##
==========================================
+ Coverage 91.28% 92.14% +0.86%
==========================================
Files 127 127
Lines 30492 30470 -22
==========================================
+ Hits 27835 28078 +243
+ Misses 2657 2392 -265 |
7b7b8b8
to
10bdcc8
Compare
9b0fd0b
to
250b744
Compare
I've confirmed this is an upstream bug
& confirmed that my one liner fix fixes this |
250b744
to
2d25dda
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe wait 1-2 days before merging to see if pgsql-hackers responds with an alternative suggestion, but otherwise seems fine.
Postgres has committed this fix to their ruleutils Updating branch to match Tom's commit |
2d25dda
to
e9f2c3d
Compare
FROM (query) alias ignored renaming In nested subqueries the select list would rename, while the join alias would not respect that
e9f2c3d
to
342d423
Compare
Great! |
Fixes #2642
FROM (query) alias ignored renaming
In nested subqueries the select list would rename, while the join alias would not respect that
DESCRIPTION: fix error caused by joins with shadowed aliases