Bug 2477 - incorrect sorting with multiple entries in ARTISTSORT field in 6.2.1 but not 6.2.0
: incorrect sorting with multiple entries in ARTISTSORT field in 6.2.1 but not ...
Status: RESOLVED DUPLICATE of bug 2456
Product: Logitech Media Server
Classification: Unclassified
Component: Database
: 6.2.1
: PC Linux (other)
: P2 normal (vote)
: ---
Assigned To: Dan Sully
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-11-03 08:34 UTC by Matthew Bell
Modified: 2011-03-16 04:24 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 Matthew Bell 2005-11-03 08:34:14 UTC
I have had Slimserver 6.2.1 (2005-10-31, 2005-11-01, 2005-11-02 releases) 
running on a machine that uses Vector Linux (Slackware based).  Tag fields were 
created in Windows using Foobar.  Tag fields are of this form:
ARTIST= Brad Shepik; Scott Colley; Ton Rainey
ARTISTSORT= ShepikBrad; ColleyScott; RaineyTom

If I set the one album with these fields as my music library in Slimserver 
6.2.1, with ';' defined as the value separator, then in Browse Artists the 
artists are displayed in this order:
Ton Rainey
Scott Colley
Brad Shepik.

Order is always the same.  When I used my full music library, I got a similar 
apparently random effect, though again the order in which artists appeared was 
always the same.

If I delete the ARTISTSORT field, the Browse Artists display is
Brad Shepik
Scott Colley
Ton Rainey.
So they are correctly sorted alphabetically according to the beginning of their 
name.

In 6.2.0, with the ARTISTSORT field in place, I get the order I want:
Scott Colley
Ton Rainey
Brad Shepik

In 6.2.1 when I search by artist, each artist can be found using either his 
first or his last name.  In 6.2.0, only the last name shows up on a search.

I haven't tested for the bug on other OS's or platforms.  I also haven't tested 
whether the bug appears only when there are multiple values in the artist and 
artistsort fields.
Comment 1 KDF 2005-11-03 09:59:31 UTC
sounds very much like bug2456
Comment 2 Dan Sully 2005-11-03 13:46:31 UTC

*** This bug has been marked as a duplicate of 2456 ***