Bug 3293 - Clear database & rescan doesn't really "clear"
: Clear database & rescan doesn't really "clear"
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Database
: 6.2.1
: PC Linux (other)
: P3 normal with 1 vote (vote)
: ---
Assigned To: Dan Sully
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-04-18 17:02 UTC by John Stimson
Modified: 2011-03-16 04:24 UTC (History)
0 users

See Also:
Category: ---


Attachments
for reference (16.39 KB, text/plain)
2006-04-25 12:25 UTC, KDF
Details

Note You need to log in before you can comment on or make changes to this bug.
Description John Stimson 2006-04-18 17:02:10 UTC
Here is a strange behavior that I experienced the other day:

I noticed that the Los Angeles Saxophone Quartet was sorted in the artist list under "A".
I found the "words to ignore when sorting" and removed "Los".
Los Angeles Saxophone Quartet was still sorted under "A".
I checked the tags for an ARTISTSORT tag.  Not present.
I rescanned "new or changed".
Los Angeles Saxophone Quartet was still sorted under "A".
I rescanned "clear and rescan from scratch".
Los Angeles Saxophone Quartet was still sorted under "A".
Repeat the last two steps a couple times just to make sure.
I terminated slimserver.
I deleted ~slim/.slimserversql.db
I started slimserver.
Los Angeles Saxophone Quartet was now sorted under "L".

Obviously, there was some residual data left in the database even though the "clear and rescan from scratch" was selected.
Comment 1 KDF 2006-04-18 17:11:51 UTC
From the "Before You Begin" section on the bugzilla front page:
"1.  Try the latest stable nightly build of SlimServer and see if the bug is still there."

Have you done that?  If so, please not above if it is 6.2.2 or 6.5b1.
thanks.
Comment 2 Cliff McCarthy 2006-04-20 07:59:41 UTC
I have observed this behaviour as well.  I have replicated it on 2.6.1 and 2.6.2.  It appears that deleting the database is not nessary to obtain the correct behaviour, but stopping and re-starting the server is.  That is, in 2.6.2, I performed the steps described here---I removed 'Los' from the list of prefixes to ignore, then re-scanned.  The ordering did not change.  After I stopped and re-started the server, the ordering was correct.
Comment 3 Dan Sully 2006-04-22 15:24:47 UTC
Please try using the latest 6.2.2 nightlies:

http://slimdevices.com/dev_nightly.html

and run with the --d_sql debugging flag turned on.

You should see something like dbdrop or dbclear being executed after you click on "Clear & Rescan"
Comment 4 KDF 2006-04-25 12:25:42 UTC
Created attachment 1199 [details]
for reference

Here is a copy of my log, d_sql using 04-25 build of 6.2.2.  Looks to be fine for me, so maybe useful for comparison.
Comment 5 Dan Sully 2006-06-06 17:17:32 UTC
Cliff / John - does this still happen with the official 6.2.2 release, or the 6.3 nightlies?

We've been unable to reproduce here.

Thanks.
Comment 6 John Stimson 2006-06-13 00:50:23 UTC
It behaves more reasonably with 6.2.2.  The example is the "Los Angeles Saxophone Quartet".  With the server running and "Articles to ignore when sorting" set to "The", the artist was sorted under L.  When I added "Los" to "Articles to ignore when sorting" and clicked change, the artist was sorted under L.  When I performed a Rescan New/Changed, the artist was sorted under L.  When I performed Clear & Rescan, the artist was sorted under A.

I had originally expected the change to take effect immediately without clearing the database, but now it's better than before, where I had to kill the server and nuke the database file.
Comment 7 Blackketter Dean 2006-06-20 11:32:57 UTC
Dan: what's the status of this?  
Comment 8 Dan Sully 2006-06-21 10:32:54 UTC
Fixed in change 8072

You'll still need to wipe & rescan, but changing the articles can be done now without needing a server restart.
Comment 9 Chris Owens 2006-06-27 14:21:45 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.