-
Notifications
You must be signed in to change notification settings - Fork 2.1k
migration from stable8.2 to stable9 #28256
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
Conversation
| } | ||
|
|
||
| if ($schema->hasTable("${prefix}file_map")) { | ||
| $schema->dropTable("${prefix}file_map"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DeepDiver1975 @PVince81 i don't know what data is in this table. Is it important, do i have to transform and put it into another table?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no - this data is not needed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔥
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
|
In the past, some apps had update routines in "apps/$appName/appinfo/update.php". We need to make sure these still exist and run on stable10. The ones I know of that I checked:
|
|
One worry is that some "update.php" code relies on other stuff being migrated first through other means. So if we put these update.php routines into migrations, I suggest to order them exactly by order of major versions. So run the update.php codes from stable9 before running the stable9.1 migrations, etc. Just to be sure. Ideal would be to also have test cases that cover whatever these update.php routines were fixing. |
The expire trash background task has been moved into the Might need to execute automatically on update?
This is a real concern. We need to add the migration steps that are here: @PVince81 should i add it to the app again? Or should we include it in the core migrations?
Background job available as Command in https://github.com/owncloud/core/blob/master/apps/files_versions/appinfo/info.xml
The CleanUp job has been removed since the tables it was cleaning do not exist anymore. TODO:
Trashbin expire during update was extracted into a command, because it can cause the update to take extremely long for large instances. This means we don't need to do this for this update. |
|
if adding stuff back to update.php is quicker then I suggest we go that route. I expect that after the OC to 10.0 migration we might remove these again at some point... |
|
I'd like to see the checkboxes here updated before merging: #28256 (comment) |
|
The storagemigration (https://github.com/owncloud/core/blob/stable9/apps/files_external/migration/storagemigrator.php) can't be added here because of missing services in the files_external app. If we want to support migrating global and user mounts, we should add those legacy services again to files_external and add it as migration there. |
that would be fine |
…der they where added which fails some expectations in tests
d3006a3 to
46c5a91
Compare
|
@phisch can you post a list of items/checkbox of the ton of testing you have done lately? |
|
and also please update the checkboxes above with the bits you have already fixed. Thanks |
|
Tested the migration for all major databases:
Looked for missing actions/migrations from Merging this PR. |
|
@phisch thanks. Will you add this separately ?
|
|
please backport this PR to stable10 |
@PVince81 yes Backport incomming. |
* added migration from stable8.2 to stable9 * addressbooks.description can be null * added missing changes from diff between migrated mysql table and native mysql table * added autoincrement, unsigned, notnull and collation explicitly * needed to set notnull to false explicitly and remove the collation definition * order mounts by storage_id, because postgres returns it not in the order they where added which fails some expectations in tests
[stable10] migration from stable8.2 to stable9 (#28256)
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description
This PR adds a migration from stable8.2 to stable9. The migration runs before the stable9 to stable10 migration, therefore it is possible to upgrade from stable8.2 to stable10 directly.
Related Issue
https://github.com/owncloud/enterprise/issues/2010
Motivation and Context
So people can update more easily.
How Has This Been Tested?
Currently only by hand, by me. Will be tested automatically. Need help from qa though!
Types of changes
Checklist: