6056 2014-03-27 11:01:01 +0000 Sorting by "Variable" in the BitBake variables table is not working as expected 2014-04-03 14:41:17 +0000 1 1 7 Build System, Metadata & Runtime Toaster toaster unspecified x86 Multiple RESOLVED WONTFIX Medium normal 1.6 M5 1 belen.barros.pena david.reyna alexandru.damian belen.barros.pena cristiana.voicu richard.purdie --- --- No (bug/feature does not impact docs) oldest_to_newest 41825 0 belen.barros.pena 2014-03-27 11:01:01 +0000 To reproduce, click on the "Variable" heading to sort in descending alphabetical order. Lower case and upper case variables are sorted independently from each other, with lower case variables coming above the upper case ones in the descending order. Is the sorting case sensitive? If it is, I don't think it should be. 41877 1 david.reyna 2014-03-27 17:39:27 +0000 As near as I can tell, there is no way from Django to modify the sorting defaults for the "orderby" operator. I do not see how this can be fixed without resorting to custom sorting. The Django documentation specifically states: "There’s no way to specify whether ordering should be case sensitive. With respect to case-sensitivity, Django will order results however your database backend normally orders them." (https://docs.djangoproject.com/en/dev/ref/models/querysets) A custom sort would have to be executed before the paginator. Since the paginator instantiates the entire table anyway, there is no change in overhead in that respect. We would just not get the sorting efficiency of the database since our code would be in Python, but the data set is not that huge. 42234 2 belen.barros.pena 2014-04-03 14:41:17 +0000 This is a very minor thing, and the fix seems quite a lot of work, so marking as won't fix as per our last conversation during the weekly call.