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
We need to think about how to migrate our db.
Usually, the schema of db evolves as development proceed and we need to update it consistently on production environment.
The text was updated successfully, but these errors were encountered:
On rails, we create one "migration" file for every update on db schema.
"migration" files typically contain directives for creating table, adding/removing columns, adding/removing indices, updating column attributes like default values or null abilities...
And they often also contain a code to update records related to schema update, like populating new columns.
"migration" files are ordered based on timestamp and supposed to be executed in that order.
Db holds a "migrations" table to record which "migration" is executed.
When a developer (or a CI) executes migration, rails sees the migrations table in the db and executes ones which are not executed yet.
We need to think about how to migrate our db.
Usually, the schema of db evolves as development proceed and we need to update it consistently on production environment.
The text was updated successfully, but these errors were encountered: