Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
user:kluong:improvement_-_use_a_database_migration_tool [2022/02/17 01:25] kluong |
user:kluong:improvement_-_use_a_database_migration_tool [2022/02/17 01:26] (current) kluong |
||
|---|---|---|---|
| Line 92: | Line 92: | ||
| Running migrate.py executes both steps automatically, and also creates some extra tables to keep track of the state of the migrations, letting us not have to worry about the current schema. | Running migrate.py executes both steps automatically, and also creates some extra tables to keep track of the state of the migrations, letting us not have to worry about the current schema. | ||
| + | |||
| + | ===== Concluding ===== | ||
| Adding tables and modifications would be much easier to audit / run in production if we had a tool like this. Migrations could run at the beginning of a the startup sequence for the gateway for example and since the changes are checked into version control they can be audited and approved with the normal workflow. | Adding tables and modifications would be much easier to audit / run in production if we had a tool like this. Migrations could run at the beginning of a the startup sequence for the gateway for example and since the changes are checked into version control they can be audited and approved with the normal workflow. | ||