View Single Post
Old 11-02-2020, 02:19 PM   #334
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,028
Karma: 4604637
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
Quote:
Originally Posted by chaley View Post
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.
Inherited plugin dating back to the calibre 0.9 days. As long as it ain't broke, I don't fix it.

But since it's broke...

Switching to gui.current_db.saved_search_names() as suggested appears to work fine. Test version in a minute.
JimmXinu is online now   Reply With Quote