UPnP Kioslave and Amarok Collection notes

[Lukas]

MySQL is really fast in storing things up, and it shouldn't count for
majority of time used in full scan. In most ocations it takes less than
0.005s for a line to store. However, as far as I remember, Amarok uses
MyISAM tables for collection (corret me if i'm wrong), that means tables
gets locked during writes. Thisa could be asily fixed, by changing engine to
InnoDB.

Even more, to minify count of writes, its is possible to feed a list of
tracks after rescan to a temporary table stored on memory, and using joins
delete removed tracks from mysql collection and add new ones. So even using
MyISMA full rescan wouldn't couse much problem :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/amarok-devel/attachments/20100515/0089c3fe/attachment.htm