Bug 197384

Summary:	amarok 2 isn't case sensitive
Product:	[Applications] amarok	Reporter:	Matze <masterunderlined>
Component:	Collections/Local	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED FIXED
Severity:	normal	CC:	ashl1future, mail, maximilian.kossick, mitchell
Priority:	VHI
Version:	2.1.1
Target Milestone:	---
Platform:	openSUSE
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Matze 2009-06-21 14:26:48 UTC

Version:           2.1.1 (using KDE 4.2.90)
Installed from:    SuSE RPMs

Amarok isn't case sensitive. I had some folders and filenames which where exactly the same, but some letters were big or small.

Example:
~/music/COR/
~/music/Cor/

Amarok just scans one of these two folders. So you can't find the files in the secons folder in the collection. If you add the songs with drag & drop, amarok doesn't scan the tags too.

If you have two files like this:
SONG.mp3
song.mp3
Amarok is scanning just one too.

Comment 1 Myriam Schweingruber 2009-06-21 18:01:05 UTC

This seems very strange to me, can somebody confirm this?

Comment 2 Alexey Shildyakov 2009-06-21 20:52:05 UTC

Confirm it on Amarok 2.1.1
I think it's related for bug with DB not the scan.

Comment 3 Alexey Shildyakov 2009-06-23 00:49:45 UTC


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

Comment 4 Myriam Schweingruber 2009-06-23 13:39:09 UTC

Alexey: no, please, do not set duplicates if you don't see the difference :(
This is not the same bug AT ALL!

Comment 5 Myriam Schweingruber 2009-06-23 13:39:32 UTC

Confirmed

Comment 6 Mark Kretschmann 2009-06-23 14:40:20 UTC

Possibly a MySQL thing. Googling for "mysql case sensitive" returns tons of pages.

Comment 7 Jeff Mitchell 2009-06-23 23:28:50 UTC

Collation in the DB is indeed case-insensitive.  This actually only matters when you use strings for primary/unique keys -- which we do  :-|

If we want to try changing this I could trawl out another DB update that changes the collation to something case-sensitive...not sure how that might affect various operations though.  Maybe it'll just make things happy.  :-)

Comment 8 Myriam Schweingruber 2009-08-10 08:40:08 UTC

*** Bug 203243 has been marked as a duplicate of this bug. ***

Comment 9 Myriam Schweingruber 2009-08-22 09:45:20 UTC

Any news on this, Jeff?

Comment 10 Jeff Mitchell 2009-08-22 15:27:37 UTC

No, it got lost in the ether. I'll look into it again when I have time.

Comment 11 Jeff Mitchell 2009-08-26 20:18:56 UTC

Looked into this a bit...something weird going on which isn't related to the collection scanning, and AFAICT isn't related to the database either, but rather somewhere in between. Also interesting: while file case-insensitivity seems to be a problem from the outset (i.e. full scan), folder case-sensitivity seems to be a problem only after an incremental scan. They'll appear on first (full) scan, but when you next open up Amarok they won't.

The reason for the incremental scanning issue is that the two different paths aren't being saved into the database. This should hopefully be easy to fix. Not sure about the files, yet.

Please be patient -- this is on high/top priority for my bugfixes before 2.2 but I'm super busy right now.

Comment 12 Jeff Mitchell 2009-09-01 19:30:57 UTC

Fixed in git commit bc00b898a72a0f5d9b6ae10f723502efc9b638c2.