Bugzilla – Bug 3719
Case sensitive artist lookup
Last modified: 2008-09-15 14:39:24 UTC
r8332 with a separate MySQL 5.0 server. Noticed that 'Christian McBride' <> 'Christian Mcbride', leading to two distinct artists in the artists list. In the contributors table there are two records - the name columns differ only in case, but namesort and namesearch are identical.
So do you have any thoughts about how Slimserver should know which one of the capitalization schemes in a music collection is 'correct'? I can envision aggravated customers if they have 9 Christian McBride albums, and 1 Christian Mcbride track they downloaded somewhere, and Slimserver is displaying all their tracks under 'Christian Mcbride?'
We can't fix your tags.
This was made the behavior in SlimServer more than a year ago. I just found the previous request, bug 1548. Sorry, maybe I should have reopened it. See also the discussions in the forums from May-June 2005. Chris, SlimServer can't know which capitilazition should be used. You either do a first-in or last-in update of the 'name' column in the contributors table and you display whatever is in the table.
It does appear to be a regression of bug 1548.
Fixed in change 8427