#19607: prefetch_related crash
-------------------------------------+-------------------------------------
Reporter: av@… | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.4
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: prefetch | Unreviewed
prefetch_related | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by lukeplant):
Thanks kenn - but I'm afraid this is really going nowhere without some
understanding of the issue, and if no-one isolates a test case, then we
probably will not understand the issue. There is no question that we want
to fix it, so an additional +1 tells us nothing.
I'm not trying to be rude, but lots of people saying "Please fix this, but
I don't have time to help", doesn't actually help us, it only takes up
time reading messages.
If someone comes up with a test case, I'm happy to pledge the time needed
to fix it. But I've never seen the error myself.
--
Ticket URL: <https://code.djangoproject.com/ticket/19607#comment:15>
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/067.76d3dadaef115d17e1e1bb15f72866b7%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
