Quote:
Originally Posted by Majutsushi
Looking at how the new DB functionality works by copying data between the device database and a temporary one (using Connection.backup()), I'm not sure the two failing database operations make sense to run on the temporary database. Vacuuming the temporary database should have no effect on the original database since it's not part of the data that would be copied, and similarly with the database checking. So the best thing I can probably do is catch the error and present a friendlier error message.
Edit: Vacuuming may not even be necessary in this situation anyway since the data copying may have a similar effect by its very nature. |
Just reminding you to catch the error if possible; seeing this functionality will be in the forthcoming Calibre 8 it would be nice to catch it sooner than later.