[BUG]: Unique constraint is not added to the change.

[theanh098]

What version of drizzle-orm are you using?

0.30.10

What version of drizzle-kit are you using?

0.21.1

Describe the Bug

When I add a new unique() constraint on a exsited column and then run drizzle-kit push, it was not applied. Furthermore, when I run drizzle-kit generate the output shows No schema changes, nothing to migrate.

Expected behavior

No response

Environment & setup

No response

[AndriiSherman]

Could you please share some repro example for this case? Would need a schema before and after changes

[achaconm2001]

Hi @AndriiSherman

I made this repo for the repro example:
https://github.com/achaconm2001/drizzle-unique-error

I placed the schema and some guides on this file:
https://github.com/achaconm2001/drizzle-unique-error/blob/main/schema.ts

The idea is to run bun run generate, then comment the current table definition that doesn't have the unique index and uncomment the definition with the index.

The expected behavior is that the first bun run generate creates the SQL to create that table, and the second bun run generate should add the unique constraint, but it doesn't detect the changes.

[AndriiSherman]

@achaconm2001 thanks a lot! I have just reproduced it and fixed it. Going to include in next patch release(tomorrow)

[AndriiSherman]

should be fixed in drizzle-kit@0.21.2. Feel free to reopen if it is not fixed for you!