[huyplb]

Ships 0.3.1. The last commit is chore: release 0.3.1, so the version-bump workflow skips this merge and main stays at 0.3.1 for the v0.3.1 tag.

Rename Column (Utilities)

• A type change is one in-place ALTER by default. The add / copy / switch-over plan is now an opt-in Large table mode (PostgreSQL, YugabyteDB, CockroachDB, MySQL, MariaDB, TiDB, SQL Server, Azure SQL).
• Size warning from the catalog estimate (about 1M rows or 1 GB) pointing at Large table mode. The data-loss check stays.
• A type change alone shows one-line "may use" warnings for routines; line-by-line references are for a rename.
• Per engine:
  • PostgreSQL family: ALTER … TYPE, adding USING only when the kind of type changes. With USING, CockroachDB refused an indexed column.
  • MySQL family: MODIFY, restating NOT NULL, the default, the collation and the comment.
  • SQL Server: one transaction that scripts the column's indexes from sys.indexes when it runs, so filters, INCLUDE and DESC survive. Large-table mode moves filtered indexes at the switch-over, because sp_rename refuses a column a filter names.
• Six engines added:
  • Oracle: MODIFY.
  • Db2: SET DATA TYPE, then a REORG.
  • SQLite: rename only.
  • DuckDB: refused while the table has an index.
  • Redshift: only lengthening a VARCHAR.
  • ClickHouse: MODIFY COLUMN, keeping Nullable; sorting-key columns refused.
• Each engine can refuse a change it cannot make, with the reason, before any SQL is shown.

Docs

• README and npm README: What's in 0.3, an Update section, and the placeholder banner removed.
• docs/releases/RELEASE_0.3.1.md (the update toast's "What's new" page), SUMMARY entry, UNRELEASED reset.
• Feature map refreshed (Rename Column card, 163 routes, re-measured counts), user guide, plan doc, DIALECTS.md.

Verification

• apps/web tsc clean; npx vitest run: 7,002 passed.
• New tests failed on the old code (A/B).
• Run live through Fox's own reader, planner, splitter and drivers on PostgreSQL, MySQL, MariaDB, TiDB, SQL Server, CockroachDB, Oracle, Db2, SQLite, DuckDB and ClickHouse.
• Not run live:
  • Redshift: the local container is plain PostgreSQL.
  • YugabyteDB: its container is stuck.
• The lockfile changes only the five version fields; npm ci --dry-run passes.

🤖 Generated with Claude Code

---

Note

Medium Risk
The PR changes generated DDL and optional in-app execution across many database engines; mistakes could block writes or mishandle indexes/constraints, though coverage is expanded (sql/web tests) and the diff documents live dialect runs.

Overview
Releases 0.3.1 and retools Utilities → Rename Column so a type change defaults to a single in-place ALTER, with the previous add/copy/switch plan available only when Large table mode is checked (eight engines). The panel loads catalog row/size estimates for a warning around ~1M rows or 1 GB, hides batch sizing unless large-table mode is on, and branches run/status messaging on a new rename / direct / copy plan mode.

The @foxschema/sql planner gains per-dialect alterTypeSteps, optional refuse reasons, columnChangeLargeTable, and six more dialect registrations (Oracle, Db2, SQLite, DuckDB, Redshift, ClickHouse), with engine-specific behavior called out in docs (e.g. SQL Server index scripting from the catalog, PostgreSQL view blocking, DuckDB indexed-table refusal). Type-shape logic moves to column-type-shape.ts for lossy conversion across dialects.

README, CLI README, 0.3.1 release notes, feature map counts, user guide, and tests/docs inventory are updated to match; unreleased notes are cleared into RELEASE_0.3.1.md.

^{Reviewed by Cursor Bugbot for commit 8e55e5a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

Test IDs

Added (1)

• column-change-large-table

{…} is a part filled in at run time. The full tree: docs/testing/TEST_IDS.md.

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 845c163e-f0a2-4b04-bb08-aa1f0cc54e13)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 28b6f6b6-5b03-4b4b-acee-da069db91963)