Breaking changes (for SQLite users)
Fixed Composite primary key order is not consistent by removing sort in SQLite and to be consistent with the same logic in PostgreSQL and MySQL
The issue that may arise for SQLite users with any driver using composite primary keys is that the order in the database may differ from the Drizzle schema.
-
If you are using
push, you MAY be prompted to update your table with a new order of columns in the composite primary key. You will need to either change it manually in the database or push the changes, but this may lead to data loss, etc. -
If you are using
generate, you MAY also be prompted to update your table with a new order of columns in the composite primary key. You can either keep that migration or skip it by emptying the SQL migration file.
If nothing works for you and you are blocked, please reach out to me @AndriiSherman. I will try to help you!
Bug fixes
- [BUG] When using double type columns, import is not inserted - thanks @Karibash
- [BUG] A number value is specified as the default for a column of type char - thanks @Karibash
- [BUG]: Array default in migrations are wrong - thanks @L-Mario564
- [FEATURE]: Simpler default array fields - thanks @L-Mario564
- [BUG]: drizzle-kit generate succeeds but generates invalid SQL for default([]) - Postgres - thanks @L-Mario564
- [BUG]: Incorrect type for array column default value - thanks @L-Mario564
- [BUG]: error: column is of type integer[] but default expression is of type integer - thanks @L-Mario564
- [BUG]: Default value in array generating wrong migration file - thanks @L-Mario564
- [BUG]: enum as array, not possible? - thanks @L-Mario564