Conversation
Ease the naming and avoid ambiguity by using standard sql terms
|
f7638be to
c11cae7
Compare
c11cae7 to
adb01b2
Compare
adb01b2 to
3342cbe
Compare
3342cbe to
8682db1
Compare
|
@AndyScherzinger this does not close #45943. It's the first of five changes |
ChristophWurst
left a comment
There was a problem hiding this comment.
- All new classes, their methods and properties require
@since 30.0.0 - All new classes require unit test coverage
d54eca5 to
9538865
Compare
9538865 to
caffae9
Compare
|
psalm error not related: #46846 |
|
when using an install made from repository (with apps/testing/ available): generate metadata from current install:
enable testing app:
delete migration from db:
preview future migrations:
|
Signed-off-by: Maxence Lange <[email protected]> d Signed-off-by: Maxence Lange <[email protected]> f Signed-off-by: Maxence Lange <[email protected]> d Signed-off-by: Maxence Lange <[email protected]>
Signed-off-by: Maxence Lange <[email protected]>
Signed-off-by: Maxence Lange <[email protected]>
Signed-off-by: Maxence Lange <[email protected]>
Signed-off-by: Maxence Lange <[email protected]>
55a5d8e to
a9e1dc6
Compare
|
/backport to stable29 |
|
@ArtificialOwl please eventually document how to use this command in a portal article, perhaps at the top of https://portal.nextcloud.com/article/Frequently-Asked-Questions/How-to-prepare-for-upgrades#content-database-migrations-between-major-versions |


tasks
new occ commands
./occ migrations:generate-metadatato create a JSON file./occ migrations:preview <version>to display migration that will be executed if an upgrade to version is initiateddetails
When adding some attributes to a migration:
will display some details when running the preview occ command:
steps to execute implemented new commands:
when using an install made from repository (with apps/testing/ available):
generate metadata from current install:
enable testing app:
delete migration from db:
preview future migrations:
result:

Checklist