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 )
is there a way to avoid/bypass this behaviour? for example, by manually specifying the name of the constraint in schema