[GH-ISSUE #7872 ] [Bug] data lost after launching 0.9.0 #3452

Author

Owner

@Thrilleratplay commented on GitHub (May 1, 2025):

Same. I am unable to import data from the existing AppFlowy data directory and when trying to switch the data directory, it creates two directories called AppFlowyDataDoNotRename and AppFlowyDataDoNotRename_beta.appflowy.cloud

@Thrilleratplay commented on GitHub (May 1, 2025): Same. I am unable to import data from the existing AppFlowy data directory and when trying to switch the data directory, it creates two directories called `AppFlowyDataDoNotRename` and `AppFlowyDataDoNotRename_beta.appflowy.cloud`

mirror commented

Author

Owner

@ancion commented on GitHub (May 1, 2025):

same problem

@ancion commented on GitHub (May 1, 2025): same problem

mirror commented

Author

Owner

@jay7x commented on GitHub (May 1, 2025):

Got the same behavior. I'd suggest to backup your data directory immediately just in case. I don't believe your data is lost (yet).

@jay7x commented on GitHub (May 1, 2025): Got the same behavior. I'd suggest to backup your data directory immediately just in case. I don't believe your data is lost (yet).

mirror commented

Author

Owner

@annieappflowy commented on GitHub (May 1, 2025):

We're looking into this issue. As long as you have these data folders, your data is safe and can be recovered.

@annieappflowy commented on GitHub (May 1, 2025): We're looking into this issue. As long as you have these data folders, your data is safe and can be recovered.

mirror commented

Author

Owner

@jay7x commented on GitHub (May 1, 2025):

⚠ Do not try this until asked by developers!!! ⚠

@annieappflowy FYI, I was able got get access to my data once by switching to Local in the Cloud Settings and restarting the app (on MacOS). Though, cannot reproduce it again after restoring from backup.

@jay7x commented on GitHub (May 1, 2025): ⚠ **Do not try this until asked by developers!!!** ⚠ @annieappflowy FYI, I was able got get access to my data **once** by switching to Local in the Cloud Settings and restarting the app (on MacOS). Though, cannot reproduce it again after restoring from backup.

mirror commented

Author

Owner

@appflowy commented on GitHub (May 1, 2025):

@jay7x Thanks. I will try to reproduce

@appflowy commented on GitHub (May 1, 2025): @jay7x Thanks. I will try to reproduce

mirror commented

Author

Owner

@jay7x commented on GitHub (May 1, 2025):

⚠ Do not try this until asked by developers!!! ⚠

@appflowy reproduced! See the steps below.

NOTES:

I'm only using AppFlowy in Local mode
I have AppFlowy data in non-default location, so that might be somehow change the process.
I'm not responsible for any data loss caused by following the steps below :)

Steps:

Starting with "Welcome to AppFlowy" page with default settings ("Cloud Settings" set to "AppFlowy Cloud")
Continue in "Anonymous mode". Should see the "Getting Started" page.
Go to Settings -> Manage data -> Reset "File storage location" to default.
Quit AppFlowy and restore original (not default) data dir from backup.
Start AppFlowy. Should see the "Getting Started" page again.
Go to Settings -> Manage data -> Import data and import data from the original data dir. AppFlowy should say that data was imported successfully, but shows no data (still "Getting Started" page only)
Go to Settings -> Cloud Settings and change Cloud Server to Local. Press "Restart". You should see an empty page with field to set the data path.
Set the data path to the original data directory. Quit AppFlowy.
Start AppFlowy. Now you should see your original data. Also File storage location should be set to the original dir (349... in my case).

@jay7x commented on GitHub (May 1, 2025): ⚠ **Do not try this until asked by developers!!!** ⚠ @appflowy reproduced! See the steps below. <details> NOTES: - I'm only using AppFlowy in Local mode - I have AppFlowy data in non-default location, so that might be somehow change the process. - I'm not responsible for any data loss caused by following the steps below :) Steps: 1. Starting with "Welcome to AppFlowy" page with default settings ("Cloud Settings" set to "AppFlowy Cloud") 2. Continue in "Anonymous mode". Should see the "Getting Started" page. 3. Go to Settings -> Manage data -> Reset "File storage location" to default. 4. Quit AppFlowy and restore original (not default) data dir from backup. 5. Start AppFlowy. Should see the "Getting Started" page again. 6. Go to Settings -> Manage data -> Import data and import data from the original data dir. AppFlowy should say that data was imported successfully, but shows no data (still "Getting Started" page only) 7. Go to Settings -> Cloud Settings and change Cloud Server to Local. Press "Restart". You should see an empty page with field to set the data path. 8. Set the data path to the original data directory. Quit AppFlowy. 9. Start AppFlowy. Now you should see your original data. Also File storage location should be set to the original dir (`349...` in my case). </details>

mirror commented

Author

Owner

@alyvusal commented on GitHub (May 1, 2025):

already tried it, it always fails. tried to import for root fodler of data folder, also from AppFlowyDataDoNotRename and also from 347750474297905152, all fails

also tried suggested by @jay7x, cannot restore data

@alyvusal commented on GitHub (May 1, 2025): already tried it, it always fails. tried to import for root fodler of data folder, also from AppFlowyDataDoNotRename and also from 347750474297905152, all fails also tried suggested by @jay7x, cannot restore data

mirror commented

Author

Owner

@LucasXu0 commented on GitHub (May 1, 2025):

@alyvusal Did you backup your original data?

@LucasXu0 commented on GitHub (May 1, 2025): @alyvusal Did you backup your original data?

mirror commented

Author

Owner

@alyvusal commented on GitHub (May 1, 2025):

@alyvusal Did you backup your original data?

yes fortunately, my data folder name inside AppFlowyDataDoNotRename fodler is 347750474297905152, but app creates new one

@alyvusal commented on GitHub (May 1, 2025): > [@alyvusal](https://github.com/alyvusal) Did you backup your original data? yes fortunately, my data folder name inside AppFlowyDataDoNotRename fodler is 347750474297905152, but app creates new one

mirror commented

Author

Owner

@LucasXu0 commented on GitHub (May 1, 2025):

We've addressed the issue and will release version v0.9.1.

If you have the original data folder 347750474297905152 and the cache.db file, we can help you recover your data. By the way, could you share your cache.db file with me so I can check the session key inside it? @alyvusal

@LucasXu0 commented on GitHub (May 1, 2025): We've addressed the issue and will release version v0.9.1. If you have the original data folder 347750474297905152 and the cache.db file, we can help you recover your data. By the way, could you share your cache.db file with me so I can check the session key inside it? @alyvusal <img width="527" alt="Image" src="https://github.com/user-attachments/assets/4d84024b-d57d-48af-95c5-36bb87cd0e82" />

mirror commented

Author

Owner

@LucasXu0 commented on GitHub (May 1, 2025):

Could you compress your data folder and email it to me(lucas.xu@appflowy.io)? I'll modify the cache.db file and send it back.

@LucasXu0 commented on GitHub (May 1, 2025): Could you compress your data folder and email it to me(lucas.xu@appflowy.io)? I'll modify the cache.db file and send it back.

mirror commented

Author

Owner

@alyvusal commented on GitHub (May 1, 2025):

data folder contains sensitive data, cache.db attached already (deleted attached file after restore was successfull)
I tried to restore from session backup table but not worked.

@alyvusal commented on GitHub (May 1, 2025): data folder contains sensitive data, cache.db attached already (deleted attached file after restore was successfull) I tried to restore from session backup table but not worked.

mirror commented

Author

Owner

@alyvusal commented on GitHub (May 1, 2025):

After opening and closing many times, try restore, this time opened new UI and showed to use anonymous mode. I imported from that windows and set my data folder, now it is ok, I see my data. But I did not got how this resolved

@alyvusal commented on GitHub (May 1, 2025): After opening and closing many times, try restore, this time opened new UI and showed to use anonymous mode. I imported from that windows and set my data folder, now it is ok, I see my data. But I did not got how this resolved

mirror commented

Author

Owner

@Dialga commented on GitHub (May 1, 2025):

same problem, following

@Dialga commented on GitHub (May 1, 2025): same problem, following

mirror commented

Author

Owner

@alyvusal commented on GitHub (May 2, 2025):

did not observe this issue on 0.9.1

@alyvusal commented on GitHub (May 2, 2025): did not observe this issue on 0.9.1

mirror commented

Author

Owner

@khorshuheng commented on GitHub (May 2, 2025):

For users who are affected by this issue, install version 0.9.1, then execute the following SQL script on cache.db (directly under the data folder, which should be in the form of <data_......>, before running the application.

UPDATE kv_table
SET value = (
  SELECT json_object(
    'user_id', json_extract(b.value, '$.user_id'),
    'user_uuid', json_extract(b.value, '$.user_uuid'),
    'workspace_id', json_extract(b.value, '$.user_workspace.id')
  )
  FROM kv_table AS b
  WHERE b.key = 'session_cache_key_backup'
)
WHERE key IN ('appflowy_session_cache', 'anon_user');

This database is in sqlite3 format. So you will need to install sqlite3, before you can run the above script, either using the command line (run sqlite3 cache.db in the terminal, after navigating to the directory) or some graphical tools for sqlite3.

Once the change has been executed, verify that the database row has been updated. Then run AppFlowy 0.9.1.

@khorshuheng commented on GitHub (May 2, 2025): For users who are affected by this issue, install version 0.9.1, then execute the following SQL script on cache.db (directly under the data folder, which should be in the form of <data_......>, before running the application. ``` UPDATE kv_table SET value = ( SELECT json_object( 'user_id', json_extract(b.value, '$.user_id'), 'user_uuid', json_extract(b.value, '$.user_uuid'), 'workspace_id', json_extract(b.value, '$.user_workspace.id') ) FROM kv_table AS b WHERE b.key = 'session_cache_key_backup' ) WHERE key IN ('appflowy_session_cache', 'anon_user'); ``` This database is in sqlite3 format. So you will need to install sqlite3, before you can run the above script, either using the command line (run sqlite3 cache.db in the terminal, after navigating to the directory) or some graphical tools for sqlite3. Once the change has been executed, verify that the database row has been updated. Then run AppFlowy 0.9.1.

mirror commented

Author

Owner

@daiyongqiang commented on GitHub (May 2, 2025):

Could you compress your data folder and email it to me(lucas.xu@appflowy.io)? I'll modify the cache.db file and send it back.

Please help me! I lost data also. I have sent an email to you. I hope for your replay.

@daiyongqiang commented on GitHub (May 2, 2025): > Could you compress your data folder and email it to me([lucas.xu@appflowy.io](mailto:lucas.xu@appflowy.io))? I'll modify the cache.db file and send it back. Please help me! I lost data also. I have sent an email to you. I hope for your replay.

mirror commented

Author

Owner

@ancion commented on GitHub (May 3, 2025):

How to recover my data! I updated 0.9.1, still show me a new workspace.

@ancion commented on GitHub (May 3, 2025): How to recover my data! I updated 0.9.1, still show me a new workspace.

mirror commented

Author

Owner

@tio-trom commented on GitHub (May 3, 2025):

In the meantime if you can restore to 0.8.8-1 and restore your app settings folder and database folder. That is what I did to get back my notes. The solution @khorshuheng posted did not work for me...

@tio-trom commented on GitHub (May 3, 2025): In the meantime if you can restore to 0.8.8-1 and restore your app settings folder and database folder. That is what I did to get back my notes. The solution @khorshuheng posted did not work for me...

mirror commented

https://github.com/AppFlowy-IO/AppFlowy/issues/7872#issuecomment-2847238877

Author

Owner

@khorshuheng commented on GitHub (May 3, 2025):

How to recover my data! I updated 0.9.1, still show me a new workspace.

If you have upgraded to 0.9.0 before, you need to follow this guide to restore your data, on top of downloading 0.9.1:

@khorshuheng commented on GitHub (May 3, 2025): > How to recover my data! I updated 0.9.1, still show me a new workspace. If you have upgraded to 0.9.0 before, you need to follow this guide to restore your data, on top of downloading 0.9.1: https://github.com/AppFlowy-IO/AppFlowy/issues/7872#issuecomment-2847238877

mirror commented

Author

Owner

@khorshuheng commented on GitHub (May 3, 2025):

In the meantime if you can restore to 0.8.8-1 and restore your app settings folder and database folder. That is what I did to get back my notes. The solution @khorshuheng posted did not work for me...

Are there any issue if you upgrade from 0.8.8-1 to 0.9.1 directly? (Just in case, keep a backup of the entire data directory)

@khorshuheng commented on GitHub (May 3, 2025): > In the meantime if you can restore to 0.8.8-1 and restore your app settings folder and database folder. That is what I did to get back my notes. The solution [@khorshuheng](https://github.com/khorshuheng) posted did not work for me... Are there any issue if you upgrade from 0.8.8-1 to 0.9.1 directly? (Just in case, keep a backup of the entire data directory)

mirror commented

Author

Owner

@tio-trom commented on GitHub (May 3, 2025):

Unfortunately yes same issues...

Upgrading appflowy-bin (0.8.8-1 -> 0.9.0-1)...
Running post-transaction hooks...
Arming ConditionNeedsUpdate...
Updating icon theme caches...
Updating the desktop file MIME type cache...
Transaction successfully finished.

Had to restore to 0.8.8-1.

And after doing that I had to remove then replace both folders for the app's settings and database. So a complete restore. Else same issue....I guess the new versions of the app are modifying files in both the storage folder and the app settings.

@tio-trom commented on GitHub (May 3, 2025): Unfortunately yes same issues... ``` Upgrading appflowy-bin (0.8.8-1 -> 0.9.0-1)... Running post-transaction hooks... Arming ConditionNeedsUpdate... Updating icon theme caches... Updating the desktop file MIME type cache... Transaction successfully finished. ``` Had to restore to 0.8.8-1. And after doing that I had to remove then replace both folders for the app's settings and database. So a complete restore. Else same issue....I guess the new versions of the app are modifying files in both the storage folder and the app settings.

mirror commented

Author

Owner

@khorshuheng commented on GitHub (May 3, 2025):

Unfortunately yes same issues...
Upgrading appflowy-bin (0.8.8-1 -> 0.9.0-1)...
Running post-transaction hooks...
Arming ConditionNeedsUpdate...
Updating icon theme caches...
Updating the desktop file MIME type cache...
Transaction successfully finished.
Had to restore to 0.8.8-1.

And after doing that I had to remove then replace both folders for the app's settings and database. So a complete restore. Else same issue....I guess the new versions of the app are modifying files in both the storage folder and the app settings.

Upgrading from 0.8.x to 0.9.0 does cause this issue, and can only be fixed by upgrading to 0.9.1 and also execute the SQL script above before launching 0.9.1.

0.8.x to be 0.9.1 (not 0.9.0) direct upgrade should be fine, however, without the need of executing the SQL script. If that is not the case, do let us know.

@khorshuheng commented on GitHub (May 3, 2025): > Unfortunately yes same issues... > > ``` > Upgrading appflowy-bin (0.8.8-1 -> 0.9.0-1)... > Running post-transaction hooks... > Arming ConditionNeedsUpdate... > Updating icon theme caches... > Updating the desktop file MIME type cache... > Transaction successfully finished. > > ``` > Had to restore to 0.8.8-1. > > And after doing that I had to remove then replace both folders for the app's settings and database. So a complete restore. Else same issue....I guess the new versions of the app are modifying files in both the storage folder and the app settings. Upgrading from 0.8.x to 0.9.0 does cause this issue, and can only be fixed by upgrading to 0.9.1 and also execute the SQL script above before launching 0.9.1. 0.8.x to be 0.9.1 (not 0.9.0) direct upgrade should be fine, however, without the need of executing the SQL script. If that is not the case, do let us know.

mirror commented

Author

Owner

@tio-trom commented on GitHub (May 3, 2025):

Upgrading from 0.8.x to 0.9.0 does cause this issue, and can only be fixed by upgrading to 0.9.1 and also execute the SQL script above before launching 0.9.1.

I see, I may give that another try. Do you think this can be fixed upstream and we can upgrade without having to manually do this database tweak? I suppose most users of this app will be very confused by manually having to fix the database.

@tio-trom commented on GitHub (May 3, 2025): > Upgrading from 0.8.x to 0.9.0 does cause this issue, and can only be fixed by upgrading to 0.9.1 and also execute the SQL script above before launching 0.9.1. I see, I may give that another try. Do you think this can be fixed upstream and we can upgrade without having to manually do this database tweak? I suppose most users of this app will be very confused by manually having to fix the database.

mirror commented

Author

Owner

@khorshuheng commented on GitHub (May 3, 2025):

Upgrading from 0.8.x to 0.9.0 does cause this issue, and can only be fixed by upgrading to 0.9.1 and also execute the SQL script above before launching 0.9.1.

I see, I may give that another try. Do you think this can be fixed upstream and we can upgrade without having to manually do this database tweak? I suppose most users of this app will be very confused by manually having to fix the database.

That's true, though at the same time, we have not been able to find a good way to do so. (Eg. The script above should not be executed for users who upgrade directly from 0.8.x to 0.9.1. Also not applicable for users who don't use anonymous mode) If we are able to, we will include this upstream. For the time being, do give the above SQL script a try. And for users who are still not able to fix this, they can send their data directory (or just cache.db, which doesn't contain the actual data) to us.

@khorshuheng commented on GitHub (May 3, 2025): > > Upgrading from 0.8.x to 0.9.0 does cause this issue, and can only be fixed by upgrading to 0.9.1 and also execute the SQL script above before launching 0.9.1. > > I see, I may give that another try. Do you think this can be fixed upstream and we can upgrade without having to manually do this database tweak? I suppose most users of this app will be very confused by manually having to fix the database. That's true, though at the same time, we have not been able to find a good way to do so. (Eg. The script above should not be executed for users who upgrade directly from 0.8.x to 0.9.1. Also not applicable for users who don't use anonymous mode) If we are able to, we will include this upstream. For the time being, do give the above SQL script a try. And for users who are still not able to fix this, they can send their data directory (or just cache.db, which doesn't contain the actual data) to us.

mirror commented

Author

Owner

@ancion commented on GitHub (May 3, 2025):

How to recover my data! I updated 0.9.1, still show me a new workspace.

If you have upgraded to 0.9.0 before, you need to follow this guide to restore your data, on top of downloading 0.9.1:

#7872 (comment)

which cache

How to recover my data! I updated 0.9.1, still show me a new workspace.

If you have upgraded to 0.9.0 before, you need to follow this guide to restore your data, on top of downloading 0.9.1:

#7872 (comment)

It must be first launch 0.9.1 ? I had already launched 0.9.1 and generate new data fold, which cache.db file should be use d to execute sql.

@ancion commented on GitHub (May 3, 2025): > > How to recover my data! I updated 0.9.1, still show me a new workspace. > > If you have upgraded to 0.9.0 before, you need to follow this guide to restore your data, on top of downloading 0.9.1: > > [#7872 (comment)](https://github.com/AppFlowy-IO/AppFlowy/issues/7872#issuecomment-2847238877) which cache > > How to recover my data! I updated 0.9.1, still show me a new workspace. > > If you have upgraded to 0.9.0 before, you need to follow this guide to restore your data, on top of downloading 0.9.1: > > [#7872 (comment)](https://github.com/AppFlowy-IO/AppFlowy/issues/7872#issuecomment-2847238877) It must be first launch 0.9.1 ? I had already launched 0.9.1 and generate new data fold, which `cache.db` file should be use d to execute sql. <img width="625" alt="Image" src="https://github.com/user-attachments/assets/3587f8e5-30b9-4148-b3b8-c25cc7415ac3" />

mirror commented

Author

Owner

@khorshuheng commented on GitHub (May 3, 2025):

The cache.db that is at the same directory as the log files. The other cache.db are generated when you try to run the import function but failed.

@khorshuheng commented on GitHub (May 3, 2025): The cache.db that is at the same directory as the log files. The other cache.db are generated when you try to run the import function but failed.

mirror commented

Author

Owner

@Thrilleratplay commented on GitHub (May 4, 2025):

I was able to recover my data with version 0.9.1with copying/moving directories and importing. This was attempting various suggestions commented here and to see how the new directory structure worked verse a copy I made after upgrading to 0.9.0, because this was random trial and error, I am not sure how to reproduce this.

@Thrilleratplay commented on GitHub (May 4, 2025): I was able to recover my data with version 0.9.1with copying/moving directories and importing. This was attempting various suggestions commented here and to see how the new directory structure worked verse a copy I made after upgrading to 0.9.0, because this was random trial and error, I am not sure how to reproduce this.

mirror commented

Author

Owner

@tio-trom commented on GitHub (May 5, 2025):

Updated from 0.8.8-1 to 0.9.1-2. Did the SQL command. Opened Appflowy same issue. Had to restore...

@tio-trom commented on GitHub (May 5, 2025): Updated from 0.8.8-1 to 0.9.1-2. Did the SQL command. Opened Appflowy same issue. Had to restore...

mirror commented

Author

Owner

@naheux commented on GitHub (May 6, 2025):

For users who are affected by this issue, install version 0.9.1, then execute the following SQL script on cache.db (directly under the data folder, which should be in the form of <data_......>, before running the application.
UPDATE kv_table
SET value = (
  SELECT json_object(
    'user_id', json_extract(b.value, '$.user_id'),
    'user_uuid', json_extract(b.value, '$.user_uuid'),
    'workspace_id', json_extract(b.value, '$.user_workspace.id')
  )
  FROM kv_table AS b
  WHERE b.key = 'session_cache_key_backup'
)
WHERE key IN ('appflowy_session_cache', 'anon_user');
This database is in sqlite3 format. So you will need to install sqlite3, before you can run the above script, either using the command line (run sqlite3 cache.db in the terminal, after navigating to the directory) or some graphical tools for sqlite3.

Once the change has been executed, verify that the database row has been updated. Then run AppFlowy 0.9.1.

I updated to 0.9.1 directly from 0.8+(forgot exact version) and met this issue after launching, solved it with sqlite3 script. Save my life!!!

@naheux commented on GitHub (May 6, 2025): > For users who are affected by this issue, install version 0.9.1, then execute the following SQL script on cache.db (directly under the data folder, which should be in the form of <data_......>, before running the application. > > ``` > UPDATE kv_table > SET value = ( > SELECT json_object( > 'user_id', json_extract(b.value, '$.user_id'), > 'user_uuid', json_extract(b.value, '$.user_uuid'), > 'workspace_id', json_extract(b.value, '$.user_workspace.id') > ) > FROM kv_table AS b > WHERE b.key = 'session_cache_key_backup' > ) > WHERE key IN ('appflowy_session_cache', 'anon_user'); > ``` > > This database is in sqlite3 format. So you will need to install sqlite3, before you can run the above script, either using the command line (run sqlite3 cache.db in the terminal, after navigating to the directory) or some graphical tools for sqlite3. > > Once the change has been executed, verify that the database row has been updated. Then run AppFlowy 0.9.1. I updated to 0.9.1 directly from 0.8+(forgot exact version) and met this issue after launching, solved it with sqlite3 script. Save my life!!!

mirror commented

Author

Owner

@gzsombor commented on GitHub (May 6, 2025):

I upgraded from 0.8.8 to 0.9.1 and all of my pages are disappeared. I had to run this query on a couple of cache.db file and switch between various folders until I noticed that I had to pick $HOME/Documents/AppFlowy as the file storage folder and not $HOME/Documents/AppFlowy/AppFlowyDataDoNotRename_aHR0cHM6Ly9iZXRhLmFwcGZsb3d5LmNsb3Vk/AppFlowyDataDoNotRename_beta.appflowy.cloud/455963427169374208 where my fixed cache.db was originally. Most confusing is that now AppFlowy displays this long path as a storage folder (even though I set to the short one).

It would be nice to see an explanation how this folder is actually used and why it is updated, etc

@gzsombor commented on GitHub (May 6, 2025): I upgraded from 0.8.8 to 0.9.1 and all of my pages are disappeared. I had to run this query on a couple of cache.db file and switch between various folders until I noticed that I had to pick `$HOME/Documents/AppFlowy` as the file storage folder and not `$HOME/Documents/AppFlowy/AppFlowyDataDoNotRename_aHR0cHM6Ly9iZXRhLmFwcGZsb3d5LmNsb3Vk/AppFlowyDataDoNotRename_beta.appflowy.cloud/455963427169374208` where my fixed cache.db was originally. Most confusing is that now AppFlowy displays this long path as a storage folder (even though I set to the short one). It would be nice to see an explanation how this folder is actually used and why it is updated, etc

mirror commented

Author

Owner

@henri9813 commented on GitHub (May 6, 2025):

Hello,

now we have the auto-updater which works nicely, why doesn’t prevent direct version upgrade but force all intermediate version to avoid upgrade which can « skip » important migrations, at this time, we talk about 0.8.8 to 0.9.1, but what will happen when a user will move from 0.9.1 to 0.1350.0 with potentially breaking change ? it will make the maintenance harder to maintain all upgrade way.

For example, i think gitlab’s way is great, you must follow all intermediate upgrade to ensure all migrations works nicely and avoid weird operations.

@henri9813 commented on GitHub (May 6, 2025): Hello, now we have the auto-updater which works nicely, why doesn’t prevent direct version upgrade but force all intermediate version to avoid upgrade which can « skip » important migrations, at this time, we talk about 0.8.8 to 0.9.1, but what will happen when a user will move from 0.9.1 to 0.1350.0 with potentially breaking change ? it will make the maintenance harder to maintain all upgrade way. For example, i think gitlab’s way is great, you must follow all intermediate upgrade to ensure all migrations works nicely and avoid weird operations.

mirror commented

Author

Owner

@mikawudi commented on GitHub (May 7, 2025):

same problem(0.8.8->0.9.1)....and any easy way to record my data?

@mikawudi commented on GitHub (May 7, 2025): same problem(0.8.8->0.9.1)....and any easy way to record my data?

mirror commented

Author

Owner

@LucasXu0 commented on GitHub (May 8, 2025):

@mikawudi did you customize the storage path or keep using the default path?

@LucasXu0 commented on GitHub (May 8, 2025): @mikawudi did you customize the storage path or keep using the default path?

mirror commented