search

pilgr / Paper

Paper is a fast NoSQL-like storage for Java/Kotlin objects on Android with automatic schema migration support.
Apache License 2.0
2.34k stars 234 forks source link

Data not persisted after migrating from v1.1 to v2.1? #120

Closed robertdo closed 6 years ago

robertdo commented 6 years ago

I recently published an update to my app where I upgraded from PaperDb v1.1 to v2.1. Now I'm seeing some reports from users saying that their data got lost after they updated. Should this be happening? Were any necessary steps required in updating PaperDb to preserve the data?

pilgr commented 6 years ago

Yes, v 2.1 had an annoying issue which could lead to data loss. It's been fixed in 2.5. https://github.com/pilgr/Paper/releases/tag/2.5

Did you have any particular reasons to not use the latest 2.6 version?

robertdo commented 6 years ago

Ah ok, makes sense. It was just an oversight that I didn't use the latest 2.6 version. So would that v2.1 issue affect every single user, most users, or just a small percentage of users? I'm trying to get an idea of how urgently I need to push a fix.

pilgr commented 6 years ago

If I recall correctly it depends on type of data. Unfortunately, if it happened once it may happen for many users with the same structure of data.

//Aleksey Masny

On Tuesday, March 13, 2018 at 23:25, robertdo wrote:

Ah ok, makes sense. It was just an oversight that I didn't use the latest 2.6 version. So would that v2.1 issue affect every single user, most users, or just a small percentage of users? I'm trying to get an idea of how urgently I need to push a fix.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub (https://github.com/pilgr/Paper/issues/120#issuecomment-372823884), or mute the thread (https://github.com/notifications/unsubscribe-auth/AAaNIdbUr3D2SZV6DzQSBxFP35fYuC5qks5teDlSgaJpZM4SpdxO).