fix: extension qualifier

[tianzhou]

Fix #144

[Copilot]

Pull Request Overview

This PR fixes type qualification handling for PostgreSQL custom types to properly distinguish between extension types and user-defined types (GitHub #144, PR #145). The key change updates SQL queries to detect extension types via pg_depend and leave them unqualified for search_path resolution, while user-defined domains and enums are schema-qualified.

• Modified type resolution logic in SQL queries to check pg_depend for extension types
• Updated test data to validate the fix using citext extension, custom domain, and enum types
• Consolidated type handling logic from separate conditions to a unified CASE expression

Reviewed Changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
ir/queries/queries.sql	Added pg_depend join and updated type qualification logic to handle extension types separately
ir/queries/queries.sql.go	Auto-generated code reflecting the SQL query changes
testdata/diff/create_table/add_column_custom_type/setup.sql	Updated test setup to use citext extension instead of composite types
testdata/diff/create_table/add_column_custom_type/new.sql	Updated test schema to include extension type, domain, and enum columns
testdata/diff/create_table/add_column_custom_type/plan.txt	Updated expected plan output to reflect new type qualification behavior
testdata/diff/create_table/add_column_custom_type/plan.sql	Updated expected DDL with qualified and unqualified type names
testdata/diff/create_table/add_column_custom_type/plan.json	Updated expected JSON plan with new columns and type names
testdata/diff/create_table/add_column_custom_type/diff.sql	Updated expected diff with qualified and unqualified type names

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.