Bug 135337 - Backslashes in song file names make them unusable with Postgres DB backend
Summary: Backslashes in song file names make them unusable with Postgres DB backend
Status: RESOLVED INTENTIONAL
Alias: None
Product: amarok
Classification: Applications
Component: Collections/Local (show other bugs)
Version: 1.4.3
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
: 137333 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-10-09 13:37 UTC by Nigel McNie
Modified: 2008-06-16 16:50 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 Nigel McNie 2006-10-09 13:37:14 UTC
Version:           1.4.3 (using KDE 3.5.4, Debian Package 4:3.5.4-3 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.18.061004

If a song file/title has a backslash in it, you can't play it or seemingly do very much with it. In some dialogs it displays wierdly, and operations seem to fail on the file (like editing artist).

The song entered the music database when I ran an import on a existing directory structure containing music, which contained the file. I can't comment on whether you can get a file with a backslash in the name in any other way.
Comment 1 Nigel McNie 2006-10-30 10:49:06 UTC
A little bit more testing shows that this occurs with the postgres database backend. After switching to the SQLite backend, the song has two backslashes in the displayed name, and plays correctly.
Comment 2 shattered 2006-12-30 22:00:36 UTC
see also bug 137333
Comment 3 Kevin Funk 2007-02-05 00:34:46 UTC
*** Bug 137333 has been marked as a duplicate of this bug. ***
Comment 4 Kevin Funk 2007-02-05 00:42:10 UTC
Works fine with the MySQL backend for me, too. Is this bug still reproducable in 1.4.4 for you?
Comment 5 Nigel McNie 2007-02-05 00:50:30 UTC
Don't know. I switched to the sqlite backend. I might be able to test this again later on.
Comment 6 Edward Hades 2008-06-15 15:50:22 UTC
Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2. Unfortunately your bug will very likely not get fixed, as the risk of regressions is too high and the Amarok developers do not have the resources for it. Thank you for your report though. Please don't hesitate to report new bugs should you have any problems with Amarok 2 once it is released.

Since amarok 2 will not work with Postgres, it is very likely, that this bug needs no more attention.
Comment 7 Edward Hades 2008-06-16 16:50:19 UTC
Thank you for your report, please come back if you encounter any bugs in amarok 2.