View Single Post
Old 03-10-2025, 07:09 AM   #132
Majutsushi
Zealot
Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'Majutsushi knows the difference between 'who' and 'whom'
 
Posts: 109
Karma: 10128
Join Date: Aug 2023
Location: New Zealand
Device: Kobo Clara HD, Kobo Libra Colour
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.

Last edited by Majutsushi; 03-10-2025 at 07:17 AM.
Majutsushi is offline   Reply With Quote