3 people reported
All time, since Jul 16, including 1 thumbs-up on GitHub.
No-op migration after kit up
“generate then diffs "old string" against "new string", sees a difference everywhere, and emits DDL — even though Postgres treats the two forms as identical.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/drizzle/issues/5053/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
First generate after drizzle-kit up emits no-op Postgres migration. Unchanged schema yields ALTER COLUMN … SET DATA TYPE … USING …, rebuilt partial indexes and recreated check constraints, forcing table rewrites.
Is this your bug?
File my report- Where
- drizzle-kit up
- Versions
- 1.0.0-rc.4 to 1.0.0-rc.5
- How bad
- Breaks a normal workflow.
Not quite your bug?
Original reports2, newest first
- Postgres:
drizzle-kit up(v7 → v9) leaves table-qualified index/check expressions and unnormalized custom types, so the firstgenerateon 1.0.0-rc.5 rebuilds every partial index and check constraint#6589 - After
drizzle-kit up(Postgres) the nextgenerateproduces a large (no-op) migration causing full rewrite#6020