"I've solved the problem by passing the returned dictionary through my own distinct() function which strips out duplicates."
Don't roll your own implementations unless you actually really need to! It's bad practise and can introduce added complexity to your solution. The .distinct() call will work fine, you just need to order correctly. Also, if you needed to do something in sql that you couldnt get to work via the django ORM i would use the new raw sql features so that you at least get back queryset objects that you can use "as is" rather than converting & flattening it to a dict and whatnot. On 21 July, 18:29, rmschne <rmsc...@gmail.com> wrote: > Yep. (as I slap my forehead). > > I read that but erroneously concluded that since I had no sort_by on > the query, I didn't pursue it. There is a default ordering in the > model. > I've solved the problem by passing the returned dictionary through my > own distinct() function which strips out duplicates. > > Thanks! -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
