Summary: | very long path names: Collection scan misses files | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | fakemon <fakemon> |
Component: | Collections/Local | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | CONFIRMED --- | ||
Severity: | wishlist | CC: | anthony, ralf-engels |
Priority: | NOR | ||
Version: | 2.5.0 | ||
Target Milestone: | 2.6 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
fakemon
2012-04-19 13:13:58 UTC
Yes, the database table has a lenght restiction for paths and it's at (I think) 320 characters. Good to know that these limits will actually be hit. a temporary fix is to just not create the index urls_id_rpath on the table urls. Than it is possible to give the rpath column in table urls the (maximal) length 1000. I do not know what the downside (presumably in speed) of this is. I didn't had any issues so far ... What is the status of this in Amarok 2.7? Moving to wishlist, as this is due to a restriction in the database and would need a change there. This hits *every* file I have stored in git-annex, which gives files names like this: ./anthony/Music/.git/annex/objects/Kw/pm/SHA512E-s27830960--a0e7606a89737a92e1fd83ab59d6d36531de59c481bc4e50f465795e02b575da62995d2285dc6f6bb4b9f165065146e9aff3b0c30249b148edb0979aa24b4567.flac/SHA512E-s27830960--a0e7606a89737a92e1fd83ab59d6d36531de59c481bc4e50f465795e02b575da62995d2285dc6f6bb4b9f165065146e9aff3b0c30249b148edb0979aa24b4567.flac That's 350 characters. (I use SHA-512 because SHA-256 is not only weaker, but *slower* on modern machines). But there is a simple fix: alter table urls modify column rpath varbinary(996); Not sure if that breaks non-ASCII characters (I have a bunch, but only in the symlink names, and Amarok is using the targets instead), but if it does, I'm not sure why Amarok wants to treat file names as text, really it ought to givem them back to the OS exactly the same as the OS gave it to Amarok. |