Specifying foreign key names in Schema

After introspecting from a database, and generating new schema with changes, the existing foreign key constraints get dropped and readded (arguably with a better name, but ignore that <a:pepe_shy:865718902628548618> ) is there a way to avoid/bypass this behaviour? for example, by manually specifying the name of the constraint in schema
No description
No description
2 Replies
sshtml
sshtml15mo ago
+1, also trying to baseline against an existing database and drizzle wants to rename all of the foreign key constraints. did you find a solution?
Angelelz
Angelelz15mo ago
There is an open issue for this. Looks like the it should be added soon. https://github.com/drizzle-team/drizzle-orm/issues/466
GitHub
[FEATURE]: Allow specifying constraint names · Issue #466 · drizzle...
Describe want to want Computed constraint names can sometimes get too long for Postgres, resulting in this warning: psql:migrations/0000_brown_rage.sql:110: NOTICE: identifier "super_duper_dup...
Want results from more Discord servers?
Add your server