feat(postgresql): add accurate analyzer mode for database-only analysis #4209
+954
−6
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
Adds an optional
analyzer.accurate: truemode for PostgreSQL that bypasses the internal catalog and uses only database-backed analysis for more accurate type information.Key Features
PREPAREstatements for all column and parameter type inferenceSELECT *andRETURNING *expansionpg_catalogto build catalog structures needed for code generation (tables, columns, enums)Configuration
Requirements
database.uriordatabase.managed: true)Files Changed
internal/config/config.goAccurate *boolto Analyzer structinternal/config/v_one.json,v_two.jsonaccurateboolean to analyzer schemainternal/engine/postgresql/analyzer/analyze.goIntrospectSchema(),EnsurePool(),GetColumnNames()methodsinternal/compiler/engine.gointernal/compiler/compile.gointernal/compiler/parse.goTest plan
🤖 Generated with Claude Code