-
-
Notifications
You must be signed in to change notification settings - Fork 514
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
Result from first window function reused by other window functions #4140
Comments
Hey Knut, thanks for reporting this one. This definitely looks like a bug where Dolt is not returning the same data as MySQL. Thanks for the good repro case; we'll dig in and see what we can find. |
Quick update... I started repro and debugging through this one on Friday and it's top of my stack today. I'll keep you updated on today's progress. |
Thanks for looking into this! |
My pleasure! This is a fun one to debug through. I had a few other meetings and reviews today, but still made some progress on this one. I found what I suspect is a simpler repro case (but could end up being a separate issue). I've got a lot more time available tomorrow to keep focused on this one and will keep you updated. |
Hey Knut, just following up... I needed to prioritize a couple of issues this week for customers with support contracts, so that preempted this work. It's still on my radar though, and we'll get back to it. |
…ources don't end up clobbering each other. Fixes dolthub/dolt#4140
@knutwannheden Thanks again for the report. I've just merged a fix for this issue. It should make it into the dolt executable some time next week. |
It looks like when a query contains multiple window functions, that the result evaluated by the first window function will also be returned by the other window functions. Take this example:
In the result set the last two columns always contain the same value, while they clearly should not (compare against https://www.db-fiddle.com/f/pQav68zxdV4gnRjcaoXdrm/0).
The text was updated successfully, but these errors were encountered: