phs
Member
So I've finally got the MySQL database working with RB after the last update, however I'm a little confused as to it's purpose.
Looking at the database schema, there doesn't appear to be any tag data stored (artist, title, genre etc), only the RB specific metadata (bpm, playcount, time markers, startdate, enddate etc).
I was expecting all the data currently stored in the XML library files would have been migrated to MySQL and used for things like the Playlist Generator. We have performance issues with the Playlist Generator (1.5 minutes to load a single 'Category' when reading 12,500 tracks from our music library XML) and I was hoping moving to MySQL meant that SQL could be used to speed up this process.
Having to still read Genre etc from the XML file has shown no noticable improvement to the Playlist Generator speed.
Is this a work in progress, or are my expectations misaligned?
Looking at the database schema, there doesn't appear to be any tag data stored (artist, title, genre etc), only the RB specific metadata (bpm, playcount, time markers, startdate, enddate etc).
I was expecting all the data currently stored in the XML library files would have been migrated to MySQL and used for things like the Playlist Generator. We have performance issues with the Playlist Generator (1.5 minutes to load a single 'Category' when reading 12,500 tracks from our music library XML) and I was hoping moving to MySQL meant that SQL could be used to speed up this process.
Having to still read Genre etc from the XML file has shown no noticable improvement to the Playlist Generator speed.
Is this a work in progress, or are my expectations misaligned?