Conversation
Pull Request Test Coverage Report for Build 8852954812Details
💛 - Coveralls |
alamb
left a comment
There was a problem hiding this comment.
Thank you very much for this contribution @jmhain -- I am truly sorry for the delay in review.
I think the approach taken by this PR looks good to me. In my opinion, all that is needed prior to merge is:
- Some additional comments (I left some suggestions)
- A few negative test cases
Thanks again for such an easy to read and review PR
|
Marking as Draft to signify this PR is no longer waiting on review. Please mark it as ready for review when it is ready for another look. |
|
@alamb Many thanks for the review feedback, I greatly appreciate it! And sorry for the delay in getting back to this. So I learned that MS SQL and Redshift both also support |
|
Just resolved conflicts on this again cc @alamb |
|
Looks like there is a conflict (perhaps with one of your other PRs 😆 ) -- if you can resolve that I'll merge this PR in. Thanks again |
|
@alamb Done, thank you! |
|
🚀 |
This adds support for the
CONNECT BYoperator, supported by Snowflake, Redshift, and MS SQL.A bit of awkwardness is the
PRIORexpressions used to refer to the upper level in theCONNECT BYrelationships. These expressions are only valid in this context, andprioris a perfectly valid identifier elsewhere. Trying to thread that context through the call stack was resulting in a massive diff, so I added some state to the parser to avoid that. Happy to change this is reviewers are not fond of that approach.