View Single Post
Old 08-29-2021, 04:55 PM   #12
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,203
Karma: 1995558
Join Date: Aug 2015
Device: Kindle
Quote:
Originally Posted by ownedbycats View Post
Question: Is it possible that the threading violation error could result in database changes no longer saving as described in this thread?


I did do a few bulk-edits with the bugged version of Last Modified activated. I checked the books and the #lastmodified datetime was written to OPF and restored with the rest of the database.
I cannot be 100% sure about this, but I don't think so. While trying to figure out the issue I replicated this error a lot of times, and the behavior you described never happened to me. And almost always it happened to only one book (When adding multiple books).

Also when testing, I restarted calibre multiple times to test various edits to the plugin, and the added books were always there. I deleted them in mass at the very end.

Still cannot be sure. I guess Kovid is better equipped to answer this.

Quote:
Originally Posted by ownedbycats View Post
I read the other thread in Development but it was not clear whether it was a silent error (which I would not have noticed as I keep the debug log minimized) or not.
Yes, the error was silent. You had to watch the debug output to notice it.
capink is offline   Reply With Quote