#22268: values_list() on a ManyToManyField returns extra None's when iterated
over.
-------------------------------------+-------------------------------------
Reporter: k_sze | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: orm, values_list, | Needs documentation: 0
ManyToManyField | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by anubhav9042):
One thing I want to clear out is that I think that {{{values}}} and
{{{values_list}}} return dictionary/tuple type data for all objects
present, hence this might not be a bug.
eg.
{{{
Class.objects.values_list()
}}}
will give you something like
{{{
[(1L, 1L, u'Software Engineering'), (2L, 1L, u'Computer Engineering')]
}}}
thus for
{{{
Class.objects.values_list('students')
}}}
you are bound to get
{{{
[(1L,), (None,)]
}}}
Thoughts??
--
Ticket URL: <https://code.djangoproject.com/ticket/22268#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.cfd3280eeb269a8fbd5ee34fbf18dee0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
