Fix compiler benchmark target SQL portability - #17
Merged
Conversation
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.
Fixes target rendering exposed by the cross-engine compiler benchmark: Spark VARCHAR/substring/interval syntax, unused synthetic rowid in COUNT(*), Feldera ARG_MIN/ARG_MAX and EXTRACT syntax, and ANSI interval literals. Adds focused Spark and Feldera regressions.\n\nValidation:\n- 45 LPTS SQL test files / 2,152 assertions\n- 3,346-file DuckDB corpus gate: no new WRONG or FAIL\n- SQLStorm 17,036 queries: 0 incorrect, 0 crashes