feat(postgres)!: the catalogue as nodes, and one introspect question per family

.github/workflows/test.yml

@@ -69,7 +69,7 @@ jobs:
       - name: Install activerecord and testsuite
         run: |
           pip install "rhosocial-activerecord @ git+https://github.com/rhosocial/python-activerecord.git@release/v1.0.0.dev30"
-          pip install "rhosocial-activerecord-testsuite @ git+https://github.com/rhosocial/python-activerecord-testsuite.git@release/v1.0.0.dev17"
+          pip install "rhosocial-activerecord-testsuite @ git+https://github.com/rhosocial/python-activerecord-testsuite.git@fix/column-constraint-gates"
 
       - name: Create postgres scenario config
         run: |
@@ -284,7 +284,7 @@ jobs:
       - name: Install activerecord and testsuite
         run: |
           pip install "rhosocial-activerecord @ git+https://github.com/rhosocial/python-activerecord.git@release/v1.0.0.dev30"
-          pip install "rhosocial-activerecord-testsuite @ git+https://github.com/rhosocial/python-activerecord-testsuite.git@release/v1.0.0.dev17"
+          pip install "rhosocial-activerecord-testsuite @ git+https://github.com/rhosocial/python-activerecord-testsuite.git@fix/column-constraint-gates"
 
       - name: Create postgres scenario config
         run: |
@@ -396,7 +396,7 @@ jobs:
       - name: Install activerecord and testsuite
         run: |
           pip install "rhosocial-activerecord @ git+https://github.com/rhosocial/python-activerecord.git@release/v1.0.0.dev30"
-          pip install "rhosocial-activerecord-testsuite @ git+https://github.com/rhosocial/python-activerecord-testsuite.git@release/v1.0.0.dev17"
+          pip install "rhosocial-activerecord-testsuite @ git+https://github.com/rhosocial/python-activerecord-testsuite.git@fix/column-constraint-gates"
 
       - name: Create postgres scenario config
         run: |
@@ -459,12 +459,12 @@ jobs:
           fail_ci_if_error: false
 
   test-postgres-19:
-    name: Python 3.14 / postgres 19beta4
+    name: Python 3.14 / postgres 19rc1
     runs-on: ubuntu-latest
 
     services:
       postgres:
-        image: postgres:19beta4
+        image: postgres:19rc1
         env:
           POSTGRES_DB: test_db
           POSTGRES_USER: root
@@ -494,7 +494,7 @@ jobs:
       - name: Install activerecord and testsuite
         run: |
           pip install "rhosocial-activerecord @ git+https://github.com/rhosocial/python-activerecord.git@release/v1.0.0.dev30"
-          pip install "rhosocial-activerecord-testsuite @ git+https://github.com/rhosocial/python-activerecord-testsuite.git@release/v1.0.0.dev17"
+          pip install "rhosocial-activerecord-testsuite @ git+https://github.com/rhosocial/python-activerecord-testsuite.git@fix/column-constraint-gates"
 
       - name: Create postgres scenario config
         run: |

.gitignore

@@ -182,3 +182,8 @@ htmlcov/
 # Claude Code temporary files (local only)
 .claude/tmp/
 .claude/plan*/
+# Worktrees for feature/* and fix/* branches. Never tracked: a `git add -A`
+# from the repo root would commit each branch's whole toolchain -- the venv, the
+# build directory and the test artifacts -- and the directory disappears when the
+# branch merges, so the history would keep a second copy of the source tree.
+.worktree/

README.md

@@ -24,7 +24,7 @@ _979088a_
 - **Python**: `>=3.8`
 - **Core**: `rhosocial-activerecord>=1.0.0.dev0,<2.0.0`
 - **Driver**: `psycopg[binary]>=3.2.13`
-- **CI-tested server versions**: 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19beta4
+- **CI-tested server versions**: 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19rc1
 - **Published**: PyPI `1.0.0.dev16`
 
 ## Installation
@@ -42,11 +42,11 @@ from uuid import UUID, uuid4
 from rhosocial.activerecord.base import FieldProxy
 from rhosocial.activerecord.backend.impl.postgres.backend import PostgresBackend
 from rhosocial.activerecord.backend.impl.postgres.config import PostgresConnectionConfig
-from rhosocial.activerecord.backend.expression import CreateTableExpression
+from rhosocial.activerecord.backend.expression import CreateTableStatement
 from rhosocial.activerecord.backend.expression.statements import (
     ColumnConstraint,
-    ColumnConstraintType,
     ColumnDefinition,
+    ColumnPrimaryKeyConstraint,
 )
 from rhosocial.activerecord.backend.expression.types import (
     ArrayType,
@@ -81,13 +81,15 @@ Article.configure(
 )
 
 dialect = Article.__backend__.dialect
-Article.__backend__.execute(*CreateTableExpression(
+Article.__backend__.execute(*CreateTableStatement(
     dialect,
     "articles",
     columns=[
         ColumnDefinition(
             dialect, "id", UUIDType(dialect),
-            constraints=[ColumnConstraint(dialect, ColumnConstraintType.PRIMARY_KEY)],
+            constraints=[ColumnConstraint(
+                dialect, branch=ColumnPrimaryKeyConstraint(dialect),
+            )],
         ),
         ColumnDefinition(dialect, "title", VarCharType(dialect, 200)),
         ColumnDefinition(dialect, "tags", ArrayType(dialect, TextType(dialect))),
@@ -179,7 +181,7 @@ operations.
 - **`RETURNING` is version-gated.** The basic clause works broadly, but
   `returning_old_new` and `update_returning_old` need PostgreSQL 18.
 - Field annotations do not drive DDL. `list[str]`, `dict` and `UUID` columns
-  are described explicitly in the `CreateTableExpression` above.
+  are described explicitly in the `CreateTableStatement` above.
 
 ## Testing
 

changelog.d/63.added.md

@@ -0,0 +1 @@
+`extensions NAME` and `views NAME` on the introspect CLI, whose type list now derives from `_TYPE_CAPABILITIES`. Typed value nodes with PostgreSQL literal spellings, and the domain formatters this backend serves are declared.

changelog.d/63.changed.md

@@ -0,0 +1 @@
+The catalogue and status questions are built from expression nodes, materialized views, sequences and extensions are statement factories, and the CLI adapts once at the entry rather than inside selected branches. A `NAME` a type cannot use is an error rather than an ignored argument.

changelog.d/63.fixed.md

@@ -0,0 +1 @@
+`table_count` comes from the same database-info row rather than a second reading, and the catalogue reports what it answered: materialized, foreign and partitioned table kinds, column dimensions, and extension facts.

changelog.d/63.internal.md

@@ -0,0 +1 @@
+The expression round-trip harness is vendored beside the matrix, live-connection checks moved out of the expression tests, and CI installs core from `release/v1.0.0.dev30` now that core #127 has merged.

docs/en_US/ddl/README.md

@@ -6,16 +6,16 @@ The PostgreSQL backend supports the same type-safe DDL expressions as the core l
 
 | Operation | PostgreSQL Support | Notes |
 |----------|-------------------|-------|
-| `CreateTableExpression` | ✅ Full | PRIMARY KEY, NOT NULL, UNIQUE, etc. |
-| `DropTableExpression` | ✅ Full | IF EXISTS, CASCADE, RESTRICT |
-| `AlterTableExpression` | ✅ Full | ADD/DROP COLUMN, ALTER COLUMN |
-| `CreateIndexExpression` | ✅ Full | Index types (BTREE, HASH, GIN, GiST, BRIN) |
-| `DropIndexExpression` | ✅ Full | |
-| `CreateViewExpression` | ✅ Full | |
-| `DropViewExpression` | ✅ Full | |
+| `CreateTableStatement` | ✅ Full | PRIMARY KEY, NOT NULL, UNIQUE, etc. |
+| `DropTableStatement` | ✅ Full | IF EXISTS, CASCADE, RESTRICT |
+| `AlterTableStatement` | ✅ Full | ADD/DROP COLUMN, ALTER COLUMN |
+| `CreateIndexStatement` | ✅ Full | Index types (BTREE, HASH, GIN, GiST, BRIN) |
+| `DropIndexStatement` | ✅ Full | |
+| `CreateViewStatement` | ✅ Full | |
+| `DropViewStatement` | ✅ Full | |
 | `PostgresCreateMaterializedViewExpression` | ✅ Full | IF NOT EXISTS, TABLESPACE, storage parameters (see [materialized views](./materialized_view.md)) |
-| `PostgresRefreshMaterializedViewExpression` | ✅ Full | CONCURRENTLY (PG 9.4+, requires a UNIQUE index) |
-| `PostgresAlterMaterializedViewExpression` | ✅ Full | RENAME TO, SET SCHEMA, SET/RESET storage parameters, OWNER TO |
+| `PostgresRefreshMaterializedViewPgStatement` | ✅ Full | CONCURRENTLY (PG 9.4+, requires a UNIQUE index) |
+| `PostgresAlterMaterializedViewStatement` | ✅ Full | RENAME TO, SET SCHEMA, SET/RESET storage parameters, OWNER TO |
 | `PostgresDropMaterializedViewExpression` | ✅ Full | IF EXISTS, CASCADE |
 | `CreatePartitionExpression` | ✅ Full | RANGE, LIST, HASH partitioning (PG 10+) |
 | `AttachPartitionExpression` | ✅ Full | Standard ATTACH PARTITION; `CONCURRENTLY` is unsupported |
@@ -30,7 +30,7 @@ The PostgreSQL backend supports the same type-safe DDL expressions as the core l
 PostgreSQL 10+ supports declarative partitioning. See [Partition Documentation](../postgres_specific_features/partition.md).
 
 ```python
-partition = PostgresCreatePartitionExpression(
+partition = PostgresCreatePartitionStatement(
     dialect, parent_table="orders", partition_name="orders_2024_q1",
     partition_type="RANGE", bounds="FROM ('2024-01-01') TO ('2024-04-01')",
 )
@@ -44,18 +44,18 @@ See [Partition Documentation](../postgres_specific_features/partition.md) for pg
 
 ```python
 from rhosocial.activerecord.backend.impl.postgres.expression.ddl.index import (
-    PostgresAlterIndexExpression, PostgresAlterIndexActionType,
-    PostgresReindexExpression,
+    PostgresAlterIndexStatement, PostgresAlterIndexActionType,
+    PostgresReindexStatement,
 )
 
 # ALTER INDEX ... RENAME TO
-alter = PostgresAlterIndexExpression(
+alter = PostgresAlterIndexStatement(
     dialect, index_name="idx_old",
     action=PostgresAlterIndexActionType.RENAME_TO("idx_new"),
 )
 
 # REINDEX CONCURRENTLY
-reindex = PostgresReindexExpression(
+reindex = PostgresReindexStatement(
     dialect, target_type="INDEX", target_name="idx_corrupted",
     concurrently=True,
 )
@@ -66,7 +66,7 @@ reindex = PostgresReindexExpression(
 PostgreSQL supports various index types:
 
 ```python
-create_idx = CreateIndexExpression(
+create_idx = CreateIndexStatement(
     dialect,
     index_name="idx_users_name",
     table_name="users",
@@ -82,7 +82,7 @@ PostgreSQL supports partial indexes with WHERE clause:
 ```python
 from rhosocial.activerecord.backend.expression import Column, Literal
 
-create_idx = CreateIndexExpression(
+create_idx = CreateIndexStatement(
     dialect,
     index_name="idx_active_users",
     table_name="users",
@@ -96,7 +96,7 @@ create_idx = CreateIndexExpression(
 PostgreSQL supports schemas:
 
 ```python
-create_table = CreateTableExpression(
+create_table = CreateTableStatement(
     dialect,
     table_name="schema_name.users",
     columns=columns

docs/en_US/ddl/materialized_view.md

@@ -13,24 +13,24 @@
 | Expression | Purpose | PostgreSQL-specific options |
 |---|---|---|
 | `PostgresCreateMaterializedViewExpression` | `CREATE MATERIALIZED VIEW` | `schema`, `if_not_exists`, `storage_options`, `tablespace`, `column_aliases`, `with_data` |
-| `PostgresRefreshMaterializedViewExpression` | `REFRESH MATERIALIZED VIEW` | `schema`, `concurrently`, `with_data` |
-| `PostgresAlterMaterializedViewExpression` | `ALTER MATERIALIZED VIEW` | `schema`, action list |
+| `PostgresRefreshMaterializedViewPgStatement` | `REFRESH MATERIALIZED VIEW` | `schema`, `concurrently`, `with_data` |
+| `PostgresAlterMaterializedViewStatement` | `ALTER MATERIALIZED VIEW` | `schema`, action list |
 | `PostgresDropMaterializedViewExpression` | `DROP MATERIALIZED VIEW` | `schema`, `if_exists`, `cascade` |
 
-The generic core expressions (`CreateMaterializedViewExpression`,
-`RefreshMaterializedViewExpression`, `DropMaterializedViewExpression`) remain
+The generic core expressions (`CreateMaterializedViewStatement`,
+`RefreshMaterializedViewStatement`, `DropMaterializedViewStatement`) remain
 usable; they simply do not carry `schema` / `if_not_exists`.
 
 ## Creating a materialized view
 
 ```python
-from rhosocial.activerecord.backend.expression import Column, FunctionCall, QueryExpression, TableExpression
+from rhosocial.activerecord.backend.expression import Column, FunctionCall, QueryStatement, TableExpression
 from rhosocial.activerecord.backend.impl.postgres.storage_parameters import PostgresStorageParameter
 from rhosocial.activerecord.backend.impl.postgres.expression.ddl import (
     PostgresCreateMaterializedViewExpression,
 )
 
-summary = QueryExpression(
+summary = QueryStatement(
     dialect=dialect,
     select=[
         Column(dialect, "product_id"),
@@ -117,19 +117,19 @@ create = PostgresCreateMaterializedViewExpression(
 
 ```python
 from rhosocial.activerecord.backend.impl.postgres.expression.ddl import (
-    PostgresRefreshMaterializedViewExpression,
+    PostgresRefreshMaterializedViewPgStatement,
 )
 
 # standard refresh
-PostgresRefreshMaterializedViewExpression(dialect=dialect, name="sales_summary")
+PostgresRefreshMaterializedViewPgStatement(dialect=dialect, name="sales_summary")
 
 # concurrent refresh — requires a UNIQUE index, rejected below PG 9.4
-PostgresRefreshMaterializedViewExpression(
+PostgresRefreshMaterializedViewPgStatement(
     dialect=dialect, name="sales_summary", schema="reporting", concurrently=True
 )
 
 # populate a WITH NO DATA view
-PostgresRefreshMaterializedViewExpression(
+PostgresRefreshMaterializedViewPgStatement(
     dialect=dialect, name="sales_daily", with_data=True
 )
 ```
@@ -145,15 +145,15 @@ creation).
 
 ```python
 from rhosocial.activerecord.backend.impl.postgres.expression.ddl import (
-    PostgresAlterMaterializedViewExpression,
+    PostgresAlterMaterializedViewStatement,
     PostgresChangeMaterializedViewOwnerAction,
     PostgresRenameMaterializedViewAction,
     PostgresResetMaterializedViewPropertiesAction,
     PostgresSetMaterializedViewPropertiesAction,
     PostgresSetMaterializedViewSchemaAction,
 )
 
-alter = PostgresAlterMaterializedViewExpression(
+alter = PostgresAlterMaterializedViewStatement(
     dialect=dialect,
     view_name="sales_summary",
     schema="reporting",
@@ -209,7 +209,7 @@ info = backend.introspector.get_materialized_view_info("sales_summary")
 exists = backend.introspector.materialized_view_exists("sales_summary")
 ```
 
-Each `ViewInfo` carries:
+Each `IntrospectionViewInfo` carries:
 
 | Field | Meaning |
 |---|---|

docs/en_US/postgres_specific_features/dialect.md

@@ -140,22 +140,22 @@ sql, params = expr.to_sql()
 PostgreSQL supports copying table structure using the `LIKE` clause with fine-grained control over what gets copied via INCLUDING/EXCLUDING options.
 
 PostgreSQL renders the clause form `CREATE TABLE t (LIKE src [INCLUDING ...])`,
-modelled by `CreateTableLikeExpression`.
+modelled by `CreateTableLikeStatement`.
 
 ```python
-from rhosocial.activerecord.backend.expression import CreateTableLikeExpression
+from rhosocial.activerecord.backend.expression import CreateTableLikeStatement
 from rhosocial.activerecord.backend.impl.postgres.dialect import PostgresDialect
 
 # Basic usage - copy table structure
-expr = CreateTableLikeExpression(
+expr = CreateTableLikeStatement(
     PostgresDialect(),
     table="users_copy",
     like_table="users",
 )
 # Generates: CREATE TABLE "users_copy" (LIKE "users")
 
 # With INCLUDING options (dictionary format - recommended)
-expr = CreateTableLikeExpression(
+expr = CreateTableLikeStatement(
     PostgresDialect(),
     table="users_copy",
     like_table="users",
@@ -168,15 +168,15 @@ expr = CreateTableLikeExpression(
 #            INCLUDING CONSTRAINTS INCLUDING INDEXES EXCLUDING COMMENTS)
 
 # With schema-qualified source table
-expr = CreateTableLikeExpression(
+expr = CreateTableLikeStatement(
     PostgresDialect(),
     table="users_copy",
     like_table=('public', 'users'),
 )
 # Generates: CREATE TABLE "users_copy" (LIKE "public"."users")
 
 # With TEMPORARY and IF NOT EXISTS
-expr = CreateTableLikeExpression(
+expr = CreateTableLikeStatement(
     PostgresDialect(),
     table="temp_users",
     like_table="users",
@@ -186,7 +186,7 @@ expr = CreateTableLikeExpression(
 # Generates: CREATE TEMPORARY TABLE IF NOT EXISTS "temp_users" (LIKE "users")
 
 # Including everything
-expr = CreateTableLikeExpression(
+expr = CreateTableLikeStatement(
     PostgresDialect(),
     table="users_copy",
     like_table="users",
@@ -207,7 +207,7 @@ expr = CreateTableLikeExpression(
 - `ALL` - Copy everything
 
 **Important Notes:**
-- `CreateTableLikeExpression` carries only the target table and source `like_table`
+- `CreateTableLikeStatement` carries only the target table and source `like_table`
 - `like_options` accepts a dict (`including`/`excluding`), a list of feature
   strings (treated as `INCLUDING`), or a list of `(action, feature)` tuples
 - Only `temporary` and `if_not_exists` flags are considered