View Single Post
Old 08-05-2013, 05:23 PM   #152
JimmXinu
Plugin Developer
JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.
 
JimmXinu's Avatar
 
Posts: 7,034
Karma: 4604637
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
Quote:
Originally Posted by kovidgoyal View Post
proceed_question() was never only about thread safety, since the updates all happen in the gui thread anyway. So you still need to use it. Think about what happens if the user has the edit metadata dialog open for a book that you are updating in the background, either the users' changes or yours would get obliterated.
True. The situation is the same with calibredb CLI updates--although probably with a smaller and more savvy user base. Oh well, I was just being hopeful.

Quote:
Originally Posted by kovidgoyal View Post
Considering that this new api took almost two years to develop, I dont think I will ever do this again But, if I do, I'll deal with any resulting confusion.
Fair enough.

I've not run into any problems using the new DB yet, but my testing has been pretty light--just day to day stuff.
JimmXinu is offline   Reply With Quote