Previous threads (http://groups.google.com/group/django-users/ browse_thread/thread/e2e7ae0ad9938d3/977e893021da52ef) have discussed the issue of ordering query sets by model method, instead of a database field. I've got a blog entry model with a pubDate, set to auto_now_add, and an option dispDate, for arbitrary display dates. A model method called getDate returns the dispDate, if there is one, or else the pubDate. This works great for displaying the date in templates, but can't be used for ordering.
The last post on the above thread has this: >A solution (or part of one) is available in magic-removal. You can >create your own custom manager, and it has a method get_query_set that >you can override. You could then create a subclass of QuerySet that >has certain methods overridden to do ordering after the data is >returned. (I think the one you'd need to override is >QuerySet._get_data). I'm comfortable with custom Managers, but I looked at the QuerySet code and don't think I can manage subclassing it. Can someone walk me through the process of making a Manager that does what I want, or point me towards some other solutions? Many thanks, Eric --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
