The ticket http://code.djangoproject.com/ticket/3397 is looking at that issue and seems to provide a good alternative for ordering non-db fields. Is that patch viable?
On Dec 2, 3:03 pm, Julien <[EMAIL PROTECTED]> wrote: > Hi all, > > I find that displaying non-db fields is quite useless if you can't > order/filter them... > > How would you approach the filtering and ordering of non-db fields in > the admin interface? Would you try to customize the newforms-admin > (and if so, how?) or add a built-in feature in the admin code? > > The way I see it is that dealing with non-db fields would involve > fetching all the data from a given table and then ordering/filtering > at a python code level. This would probably not be as fast as if done > at a database level, especially if the table contains thousands of > records, but at least that would give the ability to extend the use of > non-db fields. > > Please let me know your thoughts on this and/or pointing me to some > other similar discussions in the mailing list or elsewhere. > > Cheers! > > Julien --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
