#6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()
-------------------------------------+-------------------------------------
Reporter: Manfred Wassmann | Owner: jgelens
<manolo@…> | Status: assigned
Type: New feature | Version: SVN
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: dceu2011 | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by jgelens):
@akaariai
* Added a docstring to add_distinct_fields.
* If you specify distinct(field_list) multiple times it will overwrite the
previous one. This is the intended behavior.
* The fields in DISTINCT ON are always in the select list. I guess your
explanation can't happen. If it does could you explain further and give
some examples?
* I discussed the true_or_false argument removal with Russell and Alex
during the DjangoCon in Amsterdam this year. As it's a undocumented
feature and we couldn't find any usage of it on the web, we decided to
remove the argument. It's a weird argument anyway ;) .
--
Ticket URL: <https://code.djangoproject.com/ticket/6422#comment:58>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
