View Single Post
Old 09-12-2016, 08:52 AM   #6
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by DaltonST View Post
Kovid,

I know that you put a great premium on backward compatibility of fundamental changes to Calibre, so I would like to state that I have several plug-ins that use calibredb to automatically create new Custom Columns for the user in order for them to continue.
And as has been observed multiple times, don't do that.

Why are you using the command-line-shell wrapper around the db interface, rather than using the currently open db interface directly from python?

You are adding a great deal of complexity, and additionally making your plugins unreliable or outright broken for some of your users.
With zero benefit whatsoever.

Although you have invented a novel way to misuse calibre.

Last edited by eschwartz; 09-12-2016 at 09:18 PM. Reason: typo
eschwartz is offline   Reply With Quote