Database Migrations #34

New issue

Closed

opened 2025-05-26 08:38:31 -07:00 by VD15 · 0 comments

VD15 commented

2025-05-26 08:38:31 -07:00

Collaborator

As suggested by @munir, we should have a migrations system for the database, as it's due to change a lot over the course of development, expecially in the process of developing 2.0.

The migration system should automatically apply any unapplied schema changes to the database when run. Migrations should be performed inside a transaction, so that should an error occur mid-migration, it can be easily reverted without bricking the DB.

Each migration must have a unique number
Migrations identified by a higher number must be applied after lower numbered ones.
We can keep track of what migrations have been applied by a central schema_migrations table

As suggested by @munir, we should have a migrations system for the database, as it's due to change a lot over the course of development, expecially in the process of developing 2.0. The migration system should automatically apply any unapplied schema changes to the database when run. Migrations should be performed inside a transaction, so that should an error occur mid-migration, it can be easily reverted without bricking the DB. - Each migration must have a unique number - Migrations identified by a higher number must be applied after lower numbered ones. - We can keep track of what migrations have been applied by a central `schema_migrations` table

🎉 1