View Single Post
Old 11-02-2020, 02:07 PM   #333
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,335
Karma: 8012652
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by JimmXinu View Post
VM calls calibre.utils.search_query_parser.saved_searches() each time the VM config dialog is opened.

That method appears to be caching it's results now and giving VM the same list each time. Or else it's not using the same Saved Search cache as the rest of Calibre?
You should use db.saved_search*, which is what calibre has used since V4 and possibly before. The list of methods is found at the end of calibre.db.legacy. The same methods exist if you have a new_api db handle.
chaley is offline   Reply With Quote