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
Our migration folder can really use some help. As of now, we have 76 migrations, and it cringe-worthy to look at them. Things were introduced, removed and introduced back again, column names and types are changed again and again and again. It would make sense to keep them if we could rollback to a previous migration, however we can't. A good number of migrations is irreversible.
It would be best if we can rewrite our migration using current state of our schema. Some relevant comment can be found here.
The text was updated successfully, but these errors were encountered:
Our migration folder can really use some help. As of now, we have 76 migrations, and it cringe-worthy to look at them. Things were introduced, removed and introduced back again, column names and types are changed again and again and again. It would make sense to keep them if we could rollback to a previous migration, however we can't. A good number of migrations is irreversible.
It would be best if we can rewrite our migration using current state of our schema. Some relevant comment can be found here.
The text was updated successfully, but these errors were encountered: