MobileRead Forums - View Single Post

kovidgoyal · 05-10-2017, 03:12 PM

@DaltonST I told you a long time ago to not use calibredb.exe to make changes to the calibre database and that doing so would break eventually (not to mention that it can lead to data corruption to have calibredb and the GUI potentially making changes to the library simultaneously).

You chose not to listen -- not much I can do about that.

As for deprecating plugins, I dont see much point. If you dont plan on fixing your plugins to use the proper database API instead of calibredb, then I suggest simply removing them from the plugin index after calibre 3 is released. Or if you want to leave them around, that's fine too. You can add some code to the plugins to popup a helpful error message if they detect they are running in calibre 3.

There are a few plugins that even today have not been ported to Qt 5 and so fail to run. Your plugins will simply become a part of that set.

05-10-2017, 03:12 PM	#44
kovidgoyal creator of calibre Posts: 45,448 Karma: 27757438 Join Date: Oct 2006 Location: Mumbai, India Device: Various	@DaltonST I told you a long time ago to not use calibredb.exe to make changes to the calibre database and that doing so would break eventually (not to mention that it can lead to data corruption to have calibredb and the GUI potentially making changes to the library simultaneously). You chose not to listen -- not much I can do about that. As for deprecating plugins, I dont see much point. If you dont plan on fixing your plugins to use the proper database API instead of calibredb, then I suggest simply removing them from the plugin index after calibre 3 is released. Or if you want to leave them around, that's fine too. You can add some code to the plugins to popup a helpful error message if they detect they are running in calibre 3. There are a few plugins that even today have not been ported to Qt 5 and so fail to run. Your plugins will simply become a part of that set. Last edited by kovidgoyal; 05-10-2017 at 03:17 PM.