fix: error when table variable used in scalar context#5585
Merged
fix: error when table variable used in scalar context#5585
Conversation
Table variables defined with subqueries were silently discarded when used in scalar contexts like `filter actor_id == mod_id`, producing invalid SQL with literal identifiers. Now produces a clear error with a helpful hint. Fixes PRQL#5158 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.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
filter actor_id == mod_id), producing invalid SQL with literal identifiersRqOperatorhandling to error when relation types are used as operator argumentsFixes #5158
Test plan
test_table_variable_in_scalar_contexttest case🤖 Generated with Claude Code