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
"max", a Rails guy on Stack Overflow with a very high reputation, recently offered this advice about trying to avoid frivolous migrations. He said:
"Frivolous" migrations are less of a problem than you would think if you're actually using migrations correctly. They are only intended to live in the codebase until they have been run across environments. After that they should be deleted.
This sounds right to me, I've always wondered about the usefulness of long-obsolete migrations. Shall we delete our old migrations?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
"max", a Rails guy on Stack Overflow with a very high reputation, recently offered this advice about trying to avoid frivolous migrations. He said:
This sounds right to me, I've always wondered about the usefulness of long-obsolete migrations. Shall we delete our old migrations?
Beta Was this translation helpful? Give feedback.
All reactions