New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Library sorts track numbers as strings #5425
Comments
Commented by: bkgood |
Commented by: bkgood Oi, should mention this affects trunk. Attached patch is one possible solution, telling sqlite to sort the column as a number. In the case it can't find a number (i.e. if the first non-whilespace character is non-numeric), sqlite regards it to be 0 for the purposes of sorting (see http://www.sqlite.org/lang_expr.html ). If a string such as "1/10" is stored, it will be sorted as "1". |
Commented by: rryan Committed, thanks! |
Commented by: deftdawg ooh you guys fixed this already... That was fast! I was going to say there was some proxymodel sorting logic to handle BPMs, blank title / artist columns and stuff like that @ I suspect what you guys will probably cleaner then overriding the LessThan operator though. Cheers, -G |
Commented by: rryan Yea we don't sort in memory anymore, thank god :). On Sat, Jun 19, 2010 at 1:27 PM, ironstorm wrote:
|
Commented by: spiral6 As of Mixxx 1.10 this is broken again. |
Commented by: daschuer Mixxx 1.10 falls out of support. please upgrade to 1.11 |
Issue closed with status Fix Released. |
Reported by: bkgood
Date: 2010-06-19T19:36:05Z
Status: Fix Released
Importance: Low
Launchpad Issue: lp596345
Tags: number, sort, track
Attachments: [Screenshot of bug](https://bugs.launchpad.net/bugs/596345/+attachment/1430875/+files/Screenshot of bug), tracksort.patch
The library sorts track numbers as "1 10 2 3 4 5 ... 9" instead of "1 2 3 4 ... 9 10", because sqlite is being told to order the result set by the raw "tracknumber" column, which is stored as a string (presumably to accommodate formats which store track numbers like "1/10" for the first of a ten-number album).
See attached screenshot for example.
The text was updated successfully, but these errors were encountered: