feat: single-file-example schema change

[tianzhou]

No description provided.

[github-actions]

pgschema Plan Output

📋 Plan artifact created: pgschema-singlefile-plan-10

This plan will be used automatically when the PR is merged.

Click to expand plan details

time=2025-08-12T10:45:58.417Z level=DEBUG msg="Attempting database connection" host=localhost port=5432 database=testdb user=postgres sslmode=prefer application_name=pgschema
time=2025-08-12T10:45:58.424Z level=DEBUG msg="Database connection established successfully"
Plan: 2 to modify.

Summary by type:
  tables: 2 to modify

Tables:
  ~ orders
    - status (column)
    - orders_status_check (constraint)
  ~ users
    + age (column)
    ~ email (column.comment)
    + users_age_check (constraint)

Transaction: true

DDL to be executed:
--------------------------------------------------

ALTER TABLE orders DROP CONSTRAINT orders_status_check;

ALTER TABLE orders DROP COLUMN status;

ALTER TABLE users ADD COLUMN age integer;

ALTER TABLE users
ADD CONSTRAINT users_age_check CHECK (age >= 0);

COMMENT ON COLUMN users.email IS NULL;

---

This comment was automatically generated by the pgschema Single File Plan workflow.

[github-actions]

❌ Schema Migration Failed!

The single-file schema migration failed after merging this PR using plan pgschema-singlefile-plan-10.

This could indicate:

• Database schema changed between plan and apply (fingerprint mismatch)
• Invalid plan.json file
• Database connectivity issues

Please review the error details below:

🔍 Error Details

No output captured

Database: testdb

---

This comment was automatically generated by the pgschema Single File Apply workflow.