After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 537246 - better check db on start
better check db on start
Status: RESOLVED FIXED
Product: chronojump
Classification: Other
Component: chronojump
05
Other All
: Normal minor
: ---
Assigned To: Xavier de Blas
Xavier de Blas
Depends on:
Blocks:
 
 
Reported: 2008-06-08 13:43 UTC by Xavier de Blas
Modified: 2008-06-08 16:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Xavier de Blas 2008-06-08 13:43:25 UTC 
If chronojump db was half created or broken, don't just update from sqlite2 to sqlite3. Problably it was a bad created sqlite3 db.

A solution can be say to the user that deletes the chonojump.db. The best could be do it manually from the program just saking to confirm.