View Single Post
Old 06-29-2023, 06:53 PM   #6
capink
Wizard
capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.
 
Posts: 1,196
Karma: 1995558
Join Date: Aug 2015
Device: Kindle
Quote:
Originally Posted by chaley View Post
Depends on how the change is done. If it uses only db.cache then I don't think it will.
Quote:
Originally Posted by ownedbycats View Post
A single-field edit based on a stored GPM template. I'm not sure if that would use db.cache or not.
It uses db.new_api.set_field() to change the values.

Quote:
Originally Posted by chaley View Post
IMO removing user category items that no longer exist in the database is the correct behavior.
I don't edit my user categories directly in calibre. Instead, I edit them in a csv file, and import them into calibre using the Category Tags plugin. This might be a solution for anyone who does not want to lose their user categories.
capink is offline   Reply With Quote