Quote:
Originally Posted by ownedbycats
Suggestion: I wonder if these would be within scope to implement in Kobo Utilities:
Both of them can be done by editiing the SQLite database directly, but manually gets tiresome. If it's technically feasible, perhaps a KU menu option for selected books to run a SQLite query to overwrite, which is run prior to eject. |
That's an interesting idea, although I'm not sure how it could be implemented without either being too specific or effectively reinventing plugboards. Or do you mean actually allowing you to run an arbitrary SQL query? That would certainly be possible but also very dangerous like Terisa said. It would also have to be run in a similar manual way to what Terisa described since I don't think there's a way to hook into an eject event.
I'm curious how it's implemented in the version that Terisa uses, particularly how you can run predefined queries in an automated fashion. I can create an issue for it, but I can't promise anything especially since I'm currently in the middle of some big internal refactorings.