You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was testing the gem and ran into the same issue. The problem seems to be caused by a missing foreign_key constraint.
The code relies on the presence of FK to establish associations.
So there are currently two workarounds:
Add the missing FK constraint. Then the association IDs will be correctly assigned in the generated fixtures.
add_foreign_key:projects,:users
Manually assign the ID if adding FK is not an option (using the same method used internally to generate the deterministic IDs)
Activity
siklodi-mariusz commentedon Mar 13, 2026
I was testing the gem and ran into the same issue. The problem seems to be caused by a missing
foreign_keyconstraint.The code relies on the presence of FK to establish associations.
So there are currently two workarounds:
However, I still consider this a bug and expect this missing FK to be handled by fixturebot.
antulik commentedon Mar 14, 2026
I can confirm adding foreign keys fixes it 👍
I agree