Quote:
Originally Posted by kovidgoyal
Having lots of data in a db does not make it slow, unless the db is very poorly designed. And there is nothing preventing a plugin from using its own db if it feels like it.
|
own db is great, but the nice thing of calibre is it has already the ability to query a db so it would be nice to use this functionality.
Even good designed db's can become slow(er) but then they are TB's of size. So you're right that good designed db's are not slow. But there is no 'start-test' for plugin builders to proof they can build good db's. Your db may be good, but if a plugin builder adds own info to the db, it can slow down the complete process. If it is a plugin that runs all ways, calibre is the one to be blamed (slow program).
This combination is why it would be nice to have a second db that can be used by plugin-builders and can be queried by the calibre - API.