Rewrite information_schema.columns to return text for VARCHAR types #40
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
information_schema.columnsreturningVARCHARinstead oftextfor string columnstextorcharacter varying, but DuckDB returnsVARCHARChanges
transpiler/transform/pgcatalog.go): Rewriteinformation_schema.columns→information_schema_columns_compatserver/server.go):initInformationSchema()was never called - now called during connection setuptranspiler/transpiler_test.go): Verify the rewrite works correctlyHow it works
The
information_schema_columns_compatview (created incatalog.go) wraps DuckDB's nativeinformation_schema.columnsand converts thedata_typecolumn:CASE WHEN UPPER(data_type) = 'VARCHAR' OR UPPER(data_type) LIKE 'VARCHAR(%' THEN 'text' ELSE data_type END AS data_typeThe transpiler now rewrites queries from:
To:
Test plan
🤖 Generated with Claude Code