#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 -------------------------------------+------------------------------------- Changes (by timgraham):
* needs_better_patch: => 0 * component: Uncategorized => Database layer (models, ORM) * needs_tests: => 0 * needs_docs: => 0 * type: Uncategorized => Bug * stage: Unreviewed => Accepted Comment: I didn't attempt to reproduce but I trust the reporter. If you could transform the reproduction information into a test case for `queryset_pickle`, that's always helpful. -- Ticket URL: <https://code.djangoproject.com/ticket/27159#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 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.88bd32cd477bc08e5b60d6b56657c89a%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.