You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From time to time, the schemas of the SQLite database underpinning the client need to be adapted to meet requirements for new features. Sometimes, this includes rewriting the entire table, which can take a couple of seconds for very large accounts.
Traditionally, that migration was performed when the OCCore for an account was started, f.ex. when the user selected an account in the Files.app or the ownCloud app. But for large accounts, where migrations can take a couple of seconds, the user experience was not good, as the client seemed to "hang" or respond slowly.
PR #933 adds the ability for migrations to indicate progress. In the PR this is already used to show a progress indicator next to the selected account, until the account has finished migration.
To ensure an app extension isn't running out of memory during migration, as of PR #933 migrations are also limited to the app itself. For extensions, an error will be returned, asking the user to open the app and migrate their account.
To make that user experience even smoother, migration should ideally be performed for all accounts, in one go, at launch. Methods and APIs for this that are as lightweight as possible are already available in OCBookmark+DBMigration in the SDK.
The text was updated successfully, but these errors were encountered:
felix-schwarz
changed the title
[FEATURE REQUEST] Database migration at launch
[FEATURE REQUEST] Database migration of all accounts at launch
Mar 24, 2021
PR #933 adds the ability for migrations to indicate progress. In the PR this is already used to show a progress indicator next to the selected account, until the account has finished migration.
From time to time, the schemas of the SQLite database underpinning the client need to be adapted to meet requirements for new features. Sometimes, this includes rewriting the entire table, which can take a couple of seconds for very large accounts.
Traditionally, that migration was performed when the
OCCore
for an account was started, f.ex. when the user selected an account in the Files.app or the ownCloud app. But for large accounts, where migrations can take a couple of seconds, the user experience was not good, as the client seemed to "hang" or respond slowly.PR #933 adds the ability for migrations to indicate progress. In the PR this is already used to show a progress indicator next to the selected account, until the account has finished migration.
To ensure an app extension isn't running out of memory during migration, as of PR #933 migrations are also limited to the app itself. For extensions, an error will be returned, asking the user to open the app and migrate their account.
To make that user experience even smoother, migration should ideally be performed for all accounts, in one go, at launch. Methods and APIs for this that are as lightweight as possible are already available in
OCBookmark+DBMigration
in the SDK.The text was updated successfully, but these errors were encountered: