#27159: Pickling query from queryset causes unintended queryset evaluation
-------------------------------------+-------------------------------------
Reporter: jtiai | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by jtiai):
I added crude, initial test to {{{queryset_pickle}}} to
https://github.com/jtiai/django/tree/issue_27159
Interesting enough, if you check pickled output it's clearly visible that
it contains all instances from Parent-model.
If you compare query output as a string both are equal.
--
Ticket URL: <https://code.djangoproject.com/ticket/27159#comment:2>
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/063.d5a6be2160eb99967dcbea2ef9ad153b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
