foreign key nameing conflicts

I’m having a lot of conflicts that arise because Studio tries to use duplicate names for foreign keys in join tables. For the future, it would be good if “update database” allowed the user to pick an alternate name, rather than just flagging an error.
For now, how do I work-around this? There are lots of these duplicates in my schema. Thanks

Hi Eric,

Could you give us an example of table/field names that cause the generation of duplicated constraint names?
Also, you can edit init/update scripts right in the Studio before applying them.