32
Lost all my settings with the new update
(self.memmy)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 28 Oct 2023
32 points (100.0% liked)
Memmy - An iOS client for Lemmy
5070 readers
1 users here now
founded 1 year ago
MODERATORS
Same. Normally a mobile dev writes database migrations to keep data even after changing the SQL tables to avoid this. 🗿
I also lost all my data.
Could you elaborate on the database migrations part, if you don’t mind?
Would the migration happen when the user opens the updated app for the first time, migrating all the old sql tables to the new schema?
I’m just interested from an operational standpoint.
Yes, the migration happens when the user opens the new version of the app.
Basically you start versioning the database table schemas. If you modify tables, you say “If DB schema is moving from v2 -> v3, update these table columns in the following way…”.
This is what you’re meant to do, rather than dropping all existing tables (and data) when there’s a conflict. It’s tedious dev work but it avoids pissing off users. Using an “ORM” layer for the database can help make this sort of thing easier.
On the other hand, user preferences are probably not stored this way at all, and it’s the fact that a new app project was created from scratch that destroyed the existing user data. In Android, there’s libraries specifically for storing app user preferences that require almost no maintenance.