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 love using this gem - thank you everyone for writing and maintaining it. I have a feature request: Could we [optionally] only generate foreign-key migrations where no foreign keys are present? Then I could run
I would have certainty that I could apply the migration without breaking our main build and release process (and other migrations queued up behind mine, that my team-members are trying to run). And I'd then be able to run: rails g immigration AddRemainingKeys afterwards to see the keys where I need to address the orphan records.
The text was updated successfully, but these errors were encountered:
I love using this gem - thank you everyone for writing and maintaining it. I have a feature request: Could we [optionally] only generate foreign-key migrations where no foreign keys are present? Then I could run
I would have certainty that I could apply the migration without breaking our main build and release process (and other migrations queued up behind mine, that my team-members are trying to run). And I'd then be able to run:
rails g immigration AddRemainingKeys
afterwards to see the keys where I need to address the orphan records.The text was updated successfully, but these errors were encountered: