Migration generator splitting composite primary keys
Before, I believe the recommendation was to do
many_to_many
relationships like so:
But now this results in:
I can confirm that it is splitting these into two separate add ... primary_key: true
statements in the migrations, just spotted due to regenerating. Is there a different approach now, or is this a bug?2 Replies
That is a bug 🙂
Can you try against the main branch of ash_postgres, and see if it does the same thing?
Yep, hold on
Looks good