Ludek:

Thanks for the response, I was a little concerned why there were so many rows in the table but your explanation helped me to understand since I do use alot of queries and/or autoplaylists based on playlists. I was just VERY RELIEVED to be able to resolve this issue without losing my database.

Nyn

Nyn, thank you for reporting this

PlaylistSongs table is sometimes pre-filled, especially when querying by 'Playlist' in the situation when an AutoPlaylist is limited somehow (#Tracks, #MBs, #Minutes). Then the table is temporary pre-filled for this auto-playlist.

But true is that it should be cleared once it is not needed and fact is that it is needed only during the query. So you are right, it is a kind of garbage in your DB.

Added to my to-do list.
Will be fixed.

Thank you.

Hi:

I am using 3.0.2.1134, if i delete all the playlists from the database, shouldn't the playlistsongs table be empty? Mine has 44424 rows, is this correct??

Nyn

EDIT: With the assistance of SBondi, I was able to clear out the PlaylistSongs table, now it truly reflects my playlists. Don't know why I had 44424 entries when it should have only been 3714. Was this caused by a conversion error or a beta-testing problem, just food for thought??

Nyn