-
Notifications
You must be signed in to change notification settings - Fork 71
drop column alias resolution from HAVING clause as in PostgreSQL #6565
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
Conversation
nwt
left a comment
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.
Out of curiosity, why is it safe to set scope.lateral to true on these paths (rather than restoring whatever value it had before it was set to false)?
I think they should all work this way in sqlSelect. We are adjusting knobs in the scope that was created by sqlSelect. It's the expr recursion that should save and restore settings. |
|
I've confirmed that this addresses a problem with these 6 sqllogictest queries:
In a previous pass, I'd ensured the Now that the changes from this PR have merged to main, these all run ok and produce the same output as Postgres, still without the need for the Thanks @mccanne! |
No description provided.