New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Feature: Database Migration #388
Comments
Added Transaction & Rollback - this version includes the following changes:
These changes ensure that the migration is executed atomically, so that either all of the changes in the migration SQL are made or none of them are applied. ("all or nothing") |
…on files between local installation and latest update to make sure db is on current state
Efficient Migration Process implemented: When a migration is necessary for a particular version, the update servers will supply the required files. Each successful database migration to a new update version will be logged in the migrations table. Only migrations not present in this table will be processed. If an admin missed several updates and there is a significant difference in version numbers, the update process will scan each intermediate version to determine if a migration is required. If so, the migration file will be downloaded and installed sequentially. Further enhancements will be implemented based on feedback and requirements identified during the testing phase. |
To make sure, the database is also updated to the latest version, db migration methods will be integrated.
The text was updated successfully, but these errors were encountered: