- Commutativity checks for PostgreSQL and MySQL were updated to more accurately resolve index/table/schema footprints and preserve all open leaf parents for the next migration
- Mark mssql and @types/mssql as optional peer dependencies
- drizzle-kit generate now generates correct migrations.js file on Windows
- MSSQL real() column now returns precise values with correct mapFromDriverValue
- Object key collision issue resolved
- Migration to Cloudflare D1 now works correctly
- drizzle-kit migrate now properly displays error messages when migration SQL fails
- MS SQL Filtered Index generation no longer incorrectly generates fully qualified column names in WHERE clause
- PostgreSQL UNIQUE constraint alterations now correctly apply generated SQL changes
- Non-commutative migration false positives for create_index statements targeting different tables are now prevented
Bug fixed
-
drizzle-kit generate fails to generate correct migrations.js file on Windows
-
[BUG]: MSSQL real() column returns imprecise float64 values -- missing mapFromDriverValue
-
[BUG]: [Drizzle-kit][Pg] Altering a UNIQUE constraint: generated SQL ignores the new changes
-
[BUG]: Non-commutative migration false positive: create_index commutativity check ignores table name
-
Commutativity checks were updated for PostgreSQL and MySQL. Before,
create_indexstatements could be reported as non-commutative even when they targeted different tables, and--ignore-conflictscould still collapse multi-parent history down to a single parent. Now index/table/schema footprints are resolved more accurately, unrelated index branches are accepted, and--ignore-conflictspreserves all open leaf parents for the next migration -
fix: mark mssql and @types/mssql as optional peer dependencies