Restore problem #389
Restore problem #389
Conversation
DB is changing by restoring a backup
| } | ||
| } | ||
| } catch (e: Exception) { | ||
| Timber.i(e, "DB has changed because of restoring a backup") |
There was a problem hiding this comment.
Catching generic exceptions without properly handling them is basically always a bad idea. I also don't understand yet how this would solve the restore problems.
Basically when you import a backup into the app the database contained in the backup is stored in the internal data of the app. Then the app restarts. If a database is detected that is currently being imported the previous database is replaced by the temporary copy (imported db). When the imported database is on an older version schema it has to be migrated to the newest schema (which happens automatically). Skipping the migration (as you did here) in case an error occurs just fixes the symptom of the app crashing, but not the underlying problem.
There was a problem hiding this comment.
The problem is that the version of backup DB is 25 and it tries to migrate to 26. but, Training table has already all columns!
No description provided.