pastilhasandClaude Opus 5 e8cc90b34c name the over-long foreign keys so db:push can be a no-op ...

Drizzle generates names past Postgres's 63-character identifier limit. Postgres
stores the truncated form, drizzle compares against its own longer one, and every
push on every host drops and re-adds constraints that are already identical.

Deferred as harmless noise since 2026-08-19. What ended that was a deploy plan
saying "expect no changes, stop if it wants to alter something" — which this made
impossible to satisfy, so the deploy agent had to overrule its own instructions.

Verified by pushing twice against a scratch database: the fleet-wide second-push
churn went from ten statements to two, and the two that remain are a composite
primary key that cannot be fixed either way.

Naming a foreign key means removing the inline .references() or drizzle creates
both.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-23 14:17:04 +00:00

..

collections

name the over-long foreign keys so db:push can be a no-op

2026-08-23 14:17:04 +00:00

generations

refactor(providers): a provider is a vendor and a key, and the table is gone

2026-08-20 23:02:31 +01:00

db.ts

officer_db with atelier_ prefixes, like every other plugin

2026-08-20 17:30:53 +00:00

index.ts

refactor(providers): a provider is a vendor and a key, and the table is gone

2026-08-20 23:02:31 +01:00

schema.ts

refactor(providers): a provider is a vendor and a key, and the table is gone

2026-08-20 23:02:31 +01:00