We had a similar issue in table views, where users can highly customize
the output (like switching on/off columns, complex filtering and custom
multilevel ordering).
For the ordering issue at hand the solution was to append the pk as n-th
order directive on the queryset, if all previous fields were not unique.
I'm not sure, if this edge case can or should be handled by django
builtin logic, at least for us the condition, whether to or not to
append the pk field was not solely based on uniqueness of fields.
Cheers,
Jerch
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/5b1993ed-2e97-f7b9-9c76-d3fac31538b4%40netzkolchose.de.
