2 people reported
All time, since Aug 1.
Push recreates unchanged composite PK
“Composite primary key column ORDER is lost on introspection.”
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/4990/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
Push drops and re-adds composite primary key with no schema change. Introspection reads PK columns from information_schema.constraint_column_usage with no ORDER BY, so column order varies between runs.
Is this your bug?
File my report- Where
- drizzle-kit push
- Error text
ALTER TABLE "tag" DROP CONSTRAINT "tag_item_id_tag_pk";- Versions
- 0.45.2
- How bad
- Breaks a normal workflow.