refactor: use PostgreSqlDialect consistently for SQL parsing #55
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
Switch from GenericDialect to PostgreSqlDialect in all sqlparser usages to ensure consistency with PRQL's PostgreSQL target dialect. This eliminates potential edge cases where PostgreSQL-specific SQL syntax from PRQL compilation might not be parsed correctly.
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
GenericDialecttoPostgreSqlDialectin all sqlparser usagesWhy
k8sql presents as a PostgreSQL-compatible database:
->and->>~operatorUsing
PostgreSqlDialectthroughout eliminates potential edge cases where PostgreSQL-specific SQL syntax might not parse correctly withGenericDialect.Changes
json_path.rspreprocess.rshooks.rs