It seems that using has_many <class>, dependent: destroy in a parent model inhibits schema_associations from creating the inverse associations. As a workaround I'm using foreign_key: { on_delete: :cascade } in the child table migration file, but documentation says that the gem won't clobber additional definitions.
Please let me know if you need some additional information.
Regards,
Elias
It seems that using
has_many <class>, dependent: destroyin a parent model inhibits schema_associations from creating the inverse associations. As a workaround I'm usingforeign_key: { on_delete: :cascade }in the child table migration file, but documentation says that the gem won't clobber additional definitions.Please let me know if you need some additional information.
Regards,
Elias