On Thu, 2009-04-23 at 13:22 -0700, Tyler Erickson wrote: > I seem to be encountering the same or similar issue. The distinct() > method seems to have no affect on my queryset.
Both this post and the original one don't contain enough information for anybody to replicate the problem (since we can probably assume Django isn't, by default, broken, it's important to have enough info to rule out that the problem is with the poster's own code). In both these cases, I have one first guess as to what you are seeing: there is a big note in the documentation for distinct() pointing out that fields used in ordering are signifiant here ([1]). Could both of you check whether that is relevant? Remember that default model ordering plays a role. If so, it can be removed by calling order_by() with no parameters. Also, in both cases, checking the generated SQL would probably be useful. If you have a queryset "qs", looking at qs.query.as_sql() is the way to do that. I generally have high confidence in the correctness of distinct(). [1] http://docs.djangoproject.com/en/dev/ref/models/querysets/#distinct Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
