-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Malformed sqlite database #89
Comments
But this does not actually recover the old database right, only initializes a new one? To just get a new one, you can just delete the database while aw-server is not running and a new one will automatically be created next time aw-server starts. |
I was able to recover the majority of the database in this way. I don't know what I lost but at least I didn't had to reset everything. |
That's very interesting, thanks for the tip! |
EDIT: This comment technically relates to aw-server-rust, but it's about advice for restoring databases, so. Note - if you end up restoring your database this way, you may then encounter a problem where the rust server (maybe the python one too, haven't checked) falsely considers it to be v1, tries to upgrade it, and crashes with an error message like this one:
This is because the version is determined by the user version pragma, which seems to not be copied by |
So it happened, I have on that data from the end of 2019 and I was sad to delete but it is possible to recover the data on it.
With this commands I was able to recreate a database and now activity watch starts. In case of this issue you have aw-qt reporting an error, if you press restart server aw-qt crashes...
With the more details button you see the error on peewee about the malformed database, so you need to do those commands and restart aw-qt.
The text was updated successfully, but these errors were encountered: