Bug 3719 - Case sensitive artist lookup
: Case sensitive artist lookup
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Scanner
: 6.5b1
: PC Windows XP
: P2 minor (vote)
: ---
Assigned To: Dan Sully
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-07-09 04:20 UTC by Jim McAtee
Modified: 2008-09-15 14:39 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 Jim McAtee 2006-07-09 04:20:12 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.
Comment 1 Chris Owens 2006-07-10 11:41:03 UTC
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?'
Comment 2 Dan Sully 2006-07-10 11:42:34 UTC
We can't fix your tags.
Comment 3 Jim McAtee 2006-07-10 12:15:34 UTC
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.
Comment 4 Chris Owens 2006-07-13 14:58:33 UTC
It does appear to be a regression of bug 1548.
Comment 5 Dan Sully 2006-07-13 16:27:30 UTC
Fixed in change 8427