I see that in the latest svn checkout of qs-rf if you have a query set which has had distinct() called and then order_by() on a foreign key field you don't get the ordering on that foreign key field - the resulting generated sql query has the joins for the foreign table ready to be used for the order_by, but the "if not distinct or elt in select_aliases" bit inside get_ordering() prevents the actual ORDER BY portion being added.
I was just wondering if that's a temporary thing due to that section of code being work in progress, or whether it will be the case now that you can't use distinct with order_by on foreign key fields. Thanks, Matt --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
