-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
LEFT/RIGHT OUTER JOIN failed to detect ambiguous column reference (SQLancer-NoREC) #11408
Labels
bug
Something isn't working
Comments
Note to myself: maybe duplicate
|
Might be related to #11464 |
Not sure if this is should be classified as a bug or just as an error message that could be improved. I tested on Postgres, MySQL, and SQL Server and all fail because you cannot have duplicate table names in the FROM list. I believe the proper fix here is forcing the select t1.v1 from t1 left outer join t1 on true; variant to return the same error as select v1 from t1 left outer join t1 on true; |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Table reference in this query is ambiguous, and should be rejected by the planner.
select t1.v1 from t1 left outer join t1 on true;
Now it can be run successfully, see the reproducer:
(It can also be reproduced if 'left outer join' is changed to 'left join' 'right join' 'right outer join')
To Reproduce
No response
Expected behavior
No response
Additional context
found by SQLancer #11030
The text was updated successfully, but these errors were encountered: