Kovid, Let me remind you of my previous post above:
Quote:
|
So if a GUI plugin exrcutes a db.add_book() many times quickly, how does it now (5.7) notify Calibre to update the Cache from the physical DB so that the library_view can be subsequently updated from the refreshed Cache? That is the very real problem. 5.6 could do that. 5.7 now requires a Calibre restart to show the new books, which is unacceptable.
|
I have been using db.add_book() for years, along with the IPC call plus self.maingui.library_view.model().refresh_ids(ids)
I am now using self.maingui.library_view.model().refresh(),
instead of .refresh_ids(ids), which solves my problem of not using IPC any longer. Works fine.
Quote:
|
Let me repeat, you are not supposed to be accessing the database in ANYTHING other than the calibre process, using the calibre database API. If you do so, you will break things, and you are on your own. Good luck.
|
You have me confused with someone else. I have no clue what you are talking about, or why you are saying this to me.
Quote:
|
If you think you are going to be able to manipulate the database out from under calibre and then somehow successfully refresh the in-memory view of the database that calibre has, I'm afraid you have another think coming.
|
Ditto.
Thank you for your kind advice, although it clearly was meant for someone other than me.
DaltonST