There's no mind reading required. I have a queryset of Blog objects, not entry objects (or SQL rows for that matter). When I call distinct, I would expect a "distinct set of blog objects". Call it a strong technical point if you prefer, but I still feel this is what the common person would expect.
On Dec 4, 10:17 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Thu, 2008-12-04 at 20:15 -0800, ryan wrote: > > thanks for the thorough reply! I now understand how to proceed. > > > However, I'm not convinced that distinct shouldn't do this for me... > > It cannot read your mind. How is distinct() meant to know which of the > many multiple values it should use for ordering? Should it pick one at > random? That will only lead to disappointment, I'm sure. > > > but I understand this is a philosophical point, > > No, it's a strong technical point. To pick one value, that distinguished > value has to be well-defined (that is, there has to be a natural, > unambiguous meaning of which value to pick, for all possible > circumstances). This isn't the case here. > > Your trust is welcome (and, I'm sure, well-placed). But realise that > this isn't simply an arbitrary opinion. It's a technical constraint. > > 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
