On Thursday 13 July 2006 22:07, Luke Plant wrote: > In that particular case, yes (and in this instance it might be > possible to implement what you want be writing a custom manager and > overriding get_query_set() so that it adds a join and custom > ordering), but there is no (feasible) way of introspecting > get_last_name() and working this out, since Python functions can > contain any Python code.
Sorry, I realised I was talking at cross purposes, having forgotten the how you started the thread. If you were to provide a patch implementing that behaviour, it might be well received, but I don't think it would otherwise be on other developers's priority list. The problem is I think it might make things quite a bit more complicated, unless very nicely implemented -- going from the specific to the general makes these things harder, and the admin list view is already doing a lot. If you add too many features sometimes code can just collapse under its own weight. Luke -- "If you do a job badly enough, sometimes you don't get asked to do it again." (Calvin and Hobbes) Luke Plant || L.Plant.98 (at) cantab.net || http://lukeplant.me.uk/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
