Fix ORDER BY alias mismatch in eval gold query#2
Merged
Conversation
The constructors query in both evals_easy.json and evals_hard.json used `races_both_started` in the ORDER BY clause, but the SELECT aliases the column as `races_at_least_two_started`. This caused a DuckDB Binder Error at execution time. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
evals_easy.jsonandevals_hard.jsonwhere the constructors gold query usedraces_both_startedin theORDER BYclause, but theSELECTaliases the column asraces_at_least_two_started. This caused a DuckDBBinder Errorat execution time.Test plan
Binder Error: Referenced column "races_both_started" not found in FROM clause!Made with Cursor