No, it's directly proportional to the size of the playlist. My point always has been that size, in a well designed database should not be an issue. Indexes and the removal of many-to-many tables would help greatly. However, removing the many-to-many tables would mean code changes. A quick way round i would be to index both columns in the 'm-to-m's and also to index the corresponding columns in the parent tables. This would increase the scanning time as the indexes would nee to be populated but it would speed up retrieval.
-- 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
