We discussed internally and what we believe might be a decent compromise would be in cases where we identify that a unique-constraint maps to the join table's primary-key, we'll attempt to take the unique-constraint name and map it as the primary-key name instead. But not all databases support naming primary-keys, so in those cases, it'll be dropped. I'm going to create a follow-up jira with this enhancement and link it back.