Bug 2811 - Entries removed from genre_track with more than one playlist
: Entries removed from genre_track with more than one playlist
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Database
: 6.2.1
: All Linux (other)
: P2 normal (vote)
: ---
Assigned To: Dan Sully
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-01-11 11:17 UTC by Erland Isaksson
Modified: 2008-09-15 14:38 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erland Isaksson 2006-01-11 11:17:59 UTC
If I have more than one playlist in the playlist directory and performs a total rescan there are to few entries in the genre_track table after the rescan.

I am running this with the mysql database, and verifies the result with the following SQL statements:
select distinct tracks.id from tracks where tracks.ct='flc';
select distinct genre_track.track from genre_track;

I tested with totally 2780 tracks and 3 playlists with about 200 tracks in each and after the initial full rescan 497 tracks are missing in genre_track.

If I run the same testcase with just a single playlist in the playlist directory everything works correctly and the two SQL statements above both return 2780 rows.

My library contains .flac files only and many of them contains several genres in the GENRE tag separated with ;.

The problem also exists in "6.2.2 (2006-01-07)" but seems to be solved in "6.5 (2006-01-06)".
Comment 1 KDF 2006-04-18 01:04:11 UTC
*** Bug 2812 has been marked as a duplicate of this bug. ***
Comment 2 Dan Sully 2006-04-21 16:58:55 UTC
Erland - can you try the latest nightly 6.2.2 and us know if you still have this problem?

Thanks
Comment 3 Dan Sully 2006-06-06 16:42:13 UTC
Marking this as fixed.. if you can reproduce this in 6.3.x, please reopen.

Thanks.
Comment 4 Chris Owens 2006-06-27 14:21:42 UTC
This bug fix is now part of a released version, and so has been marked closed. If you are still experiencing this problem, please reopen the bug.