#26600: map says a queryset is not iterable
-------------------------------------+-------------------------------------
Reporter: ihucos | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: queryset iterator | Triage Stage:
map | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Philipp, if you hit a similar exception that means `map` must be involved
somehow.
If you didn't call it yourself then it's likely caused by a usage of `map`
internally in the queryset iteration code.
In this case the ticket resolution still stands, Python 2 `map`'s
shadowing of the underlying exception makes it impossible to determine its
true nature and thus we cannot conclude Django is at fault. As mentioned
previously this should all be solved on Python 3 where `map` doesn't
exhibit this behaviour.
By the way an `in` operation on a queryset you are disposing off is likely
to trigger a `MemoryError` just like in the original report. I'd suggest
you opt for something along `queryset.filter(pk=instance.pk).exists()`
instead.
--
Ticket URL: <https://code.djangoproject.com/ticket/26600#comment:11>
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/064.57617ee625eaff5ab8122f3958213c1f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
