🎉 Added support for UNIQUE constraints in PostgreSQL, MySQL, SQLite
Drizzle Kit now properly handles unique constraints for each dialect. In PostgreSQL and MySQL, they will be created as UNIQUE constraints, while in SQLite, they will be created as UNIQUE INDEX statements. According to the SQLite documentation, unique constraints are treated as unique indexes. Therefore, in the ORM and Kit, we handle unique constraints for SQLite as unique indexes
🎉 Collision detection for unique keys
We are introducing collision detection for unique keys as part of the new wave of drizzle-kit improvements. Currently, if drizzle-kit finds any unique constraints with the same name, you will receive a warning and identify the places where those names were defined by mistake. In the upcoming releases, we will further enhance this feature by adding collision checks for column names, other constraints, and more collisions and database-specific limitations.
