Okay, since it would obviously mean a major rewrite to adodpt a different database structure, how about this for a suggestion:
The Playlist table doesn't really need to be coupled to the rest of the database as it is just a list of tracks to be played. The columns required are Playlist name, Sequence no., Artist, Album, Track and File Location (maybe Artwork location as well). Every column can have it's own Index but it doesn't need to be linked to the rest of the tables in any way as i's only function is to play the tracks. Given that the rest of the tables take a long time to create at Scan time and that information is used for creating the Playlists, not other references to the parent tables should be required at run time. Any thoughts? -- larrettp ------------------------------------------------------------------------ larrettp's Profile: http://forums.slimdevices.com/member.php?userid=10191 View this thread: http://forums.slimdevices.com/showthread.php?t=45261 _______________________________________________ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
