View Single Post
Old 09-12-2016, 07:38 AM   #5
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,427
Karma: 27757236
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
@JimmXinu: set_custom and set_metadata dont operate ont he db so there is no question of notifying the GUI

@DaltonST: The correct way for a plugin to access/modify the db is to use the python db apis, not calibredb. However, as I said in my original post, the current design of calibredb which opens the database separately will be replaced by one that connects to a running instance of the calibre GUI/calibre server via IPC to perform its actions. So adapting your plugins would be as simple as passing in an extra parameter such as

--use-running-server

to calibredb.
kovidgoyal is online now   Reply With Quote