-
Notifications
You must be signed in to change notification settings - Fork 138
fix: Avoid implicit join when using join with unnest #924
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
@chalmerlowe / @Linchin, |
8fd2459
to
d12407e
Compare
Hi @snapiri, cover test is also failing
|
When using JOIN with UNNEST statements, and then creating a SELECT statement based on it, the UNNESTed table will appear twice in the FROM clause, causing an implicit join of the table with itself
d12407e
to
8467014
Compare
Hi @Linchin, Thanks for the feedback. |
@tswast / @Linchin / @chalmerlowe |
@tswast - Not sure I know how to read the
Also I see that there were 6 runs where the first failed and the 2-6 succeeded. Anything I should change? |
@snapiri That looks like a backend issue, not anything related to this code. I'll trigger a re-run. |
When using JOIN with UNNEST statements, and then creating a SELECT statement based on it, the UNNESTed table will appear twice in the FROM clause, causing an implicit join of the table with itself
Sample of problematic code:
Generates the following output:
Co-Authored-By: @yuval-bavli
Fixes #368