2015-11-22, 07:59
If I understand the way the existing cdART Manager version works correctly, the main reason it uses a separate database is for the storage of MBID's (if found/matched). It might be faster therefore to get rid of the cdART Manager database and inject the MBID values directly into Kodi's own database. Not only would this save time during the scanning stage, it would also help those of us who have multiple systems running MySQL/MariaDB where currently we have to either copy cdART Manager's database or rebuild it on each system we might want to run the addon with. That's not possible at the moment, but I'm assuming here that 'Jarvis' will have a relevant field (or fields) in the database for artist MBID's which can be manipulated which isn't currently the case.
I don't see the need for a database just for storage of previously downloaded artwork. The folders / library itself can be queried to see what has artwork of each type present, and what is missing, in addition to using the missing.txt file that can already be created on each run.
Just an idea.
I don't see the need for a database just for storage of previously downloaded artwork. The folders / library itself can be queried to see what has artwork of each type present, and what is missing, in addition to using the missing.txt file that can already be created on each run.
Just an idea.