Bug 203243 - Changing case of meta-data information is not commited
Summary: Changing case of meta-data information is not commited
Status: RESOLVED DUPLICATE of bug 187532
Alias: None
Product: amarok
Classification: Applications
Component: Collections/Local (show other bugs)
Version: 2.3-GIT
Platform: openSUSE Unspecified
: NOR critical
Target Milestone: 2.3.1
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-10 00:49 UTC by Philipp Wagner
Modified: 2009-10-03 10:52 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Wagner 2009-08-10 00:49:22 UTC
Version:           2.1.1 (using KDE 4.3.0)
Installed from:    SuSE RPMs

When I only change the case of a field in the meta-data, the change is not taken.

Steps to reproduce:

* Open the "Edit Metadata" dialog on any song
* Change only the case of the artist's name (e.g. from "PUR" to "Pur")
* Click "Save & Close"
* Open the "Edit Metadata" dialog again and see that the artist is still called "PUR"

This is the same for any metadata field I've tried (e.g. song title).
Comment 1 Myriam Schweingruber 2009-08-10 08:40:08 UTC

*** This bug has been marked as a duplicate of bug 197384 ***
Comment 2 Elias Probst 2009-09-22 22:56:40 UTC
IMHO, bug 197384 isn't really a DUP of this one.
Anyways, both are closed and it seems this happens again.

Running latest git here (e10ca0487799effccb7ec2c6f9f290383f77693a) and renaming an album (The resistance → The Resistance) doesn't update anything at all.

This change is just completely ignored.

I'm using taglib 1.6.
Comment 3 Jeff Mitchell 2009-09-23 13:19:55 UTC
The title of bug 197384 is correct -- it was just a different actual problem.

If you have a number of songs by one artist then whichever case of the artist gets picked up first is the one that sticks, because the database collation is case-insensitive. Whether that's desirable or not depends -- chances are it means you want to sanitize your tags, as I don't know anyone that actually wants The Beatles/THe BeATles/THE BEATLES in their collection. Of course, making it case sensitive means it will help you fix your collection, so there's a good argument for that -- but post 2.2, as it's way too late for 2.2 to introduce a change that could have such large potential side effects (not that I expect them, but have no idea what they could be). This could be examined for 2.2.1 (if there is such a release) or 2.3.

Now, as for the tag dialog itself: don't use it to change albums or artists, including changing the album or artist of a specific track. Use another tag editor. I don't really know the code, but last I looked at it I didn't get a fuzzy feeling that all the bugs were fully shaken out, and since I've taken great pains since 2.1 to try to fix any bugs reported in the SQL collection, trust me when I say that something about the bugs I have seen where people use the Tag Dialog to change the album or artist seems wrong, but I can't yet put my finger on it. I'm hoping someone -- which I suppose might be me if I have the time -- fully rewrites it for 2.3, instead of leaving it as mostly a port from 1.x.
Comment 4 Myriam Schweingruber 2009-10-03 10:52:30 UTC

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