#28560: distinct() on None values
-------------------------------------+-------------------------------------
Reporter: felixxm | Owner: felixxm
Type: Bug | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: distinct values | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by felixxm):
Issue is related with ordering. After `distinct()` columns from `ORDER BY`
clause are added to a `SELECT`. It doesn't take into account restricted
list of columns from `values` or `values_list`. `None` doesn't matter.
--
Ticket URL: <https://code.djangoproject.com/ticket/28560#comment:1>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.c2bb9103e9e8e85dd288d70be449c323%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
