View Single Post
Old 01-22-2023, 03:46 AM   #2
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,377
Karma: 27230406
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
use set_pref with a namespace of your plugin import name, to store library wide metadata.

There is no facility for storing per book key/value metadata with arbitrary key sets other than identifiers. But you probably shouldn't overload those as that is likely to affect performance in many places. You can simply create a new table in the sqlite database (use a unique table name) or use a custom column storing the key values serialized to text.
kovidgoyal is offline   Reply With Quote