Hello, I posted this StackOverflow question <https://stackoverflow.com/q/76425892/67579>, and @Willem Van Onsem <https://code.djangoproject.com/query?status=!closed&reporter=KommuSoft> tried to help by opening a ticket numbered #34646 <https://code.djangoproject.com/ticket/34646>, and creating a patch for supporting the order by multiple fields in admin.display decorator.
But it got closed as a duplicate of #31975 <https://code.djangoproject.com/ticket/31975> which was reported about 3 years ago, and it got closed as wontfix by @Mariusz Felisiak <https://github.com/felixxm> because he said: *"We don't want to add unnecessary complexity to the API.".* And I agree with what @Petr Dlouhý <https://code.djangoproject.com/query?status=!closed&reporter=PetrDlouhy> says: *"it is small modification of Django code and small increase in API complexity (which is consistent with the logic of other order fields, BTW)."**.* The inconsistency is when somewhere we're able to order by multiple fields, and somewhere else we can't. If we can order by multiple fields in the modelAdmin classes, why can't we do so in the admin.display decorator? So, I do hope to reconsider implementing the patch <https://code.djangoproject.com/attachment/ticket/34646/django_ordering.py.diff> that @Willem Van Onsem <https://code.djangoproject.com/query?status=!closed&reporter=KommuSoft> created. Thanks -- 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/60b18b91-935b-432c-940d-6a25ebb4f6a6n%40googlegroups.com.
