5920 2014-03-06 15:52:49 +0000 Secondary sorting criteria not working 2014-04-02 11:35:11 +0000 1 1 7 Build System, Metadata & Runtime Toaster toaster unspecified x86 Multiple VERIFIED FIXED Medium normal 1.6 M5 1 belen.barros.pena david.reyna alexandru.damian belen.barros.pena cristiana.voicu jessica.zhang --- --- No (bug/feature does not impact docs) oldest_to_newest 40925 0 belen.barros.pena 2014-03-06 15:52:49 +0000 When you sort a column where values are not unique (for example, Section or License) we need a second sorting criteria to use for the subset of values that share the same first column value. Second sorting criteria are specified as needed in the sorting design specifications (see attachments in bug 4255, bug 4264, bug 4280, bug 4298, bug 4327, bug 4383 and bug 4387). 40926 1 belen.barros.pena 2014-03-06 15:53:31 +0000 toaster/master:213fef6e87cbf60d773e28d31653e3c626d4058e 41734 2 david.reyna 2014-03-26 06:03:09 +0000 According to the Django documentation: "To order by multiple fields (where the second field is used to disambiguate ordering in cases where the first is the same), use multiple arguments: That is, the correct invocation is: order_by('bedrooms', 'bathrooms')." So, the solution is to add a "ordering_secondary" parameter to "_get_queryset", and have each class pass its respective secondary sort column name. 42112 3 david.reyna 2014-04-02 07:01:16 +0000 commit 4638e52ed2e146c43890dc9fba28031f6cc583ad 42154 4 belen.barros.pena 2014-04-02 11:35:11 +0000 verified in master:3e528d3e4bc542ca2f654c54363c56af0fb9f61b