Database migration schema is getting bigger and as it runs in a single transaction, posgres server can run out of memory.
Proposed solution
Split migrations to multiple files (per change)
Name files using numbers incrementally
Apply only changes that are necessary - Migration also handles projects. if a project from an older version is imported using make restore we need to be able to trigger all migrations again regardless the current latest version.
Database migration schema is getting bigger and as it runs in a single transaction, posgres server can run out of memory.
Proposed solution
Apply only changes that are necessary- Migration also handles projects. if a project from an older version is imported usingmake restore
we need to be able to trigger all migrations again regardless the current latest version.