#25361: Unpickling of QuerySet fails in presence of abstract intermediate model
-------------------------------------+-------------------------------------
Reporter: bronger | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8
(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 charettes):
* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
I guess we should special case fields of abstract models in
[https://github.com/django/django/blob/a7901c2e090d720ef0427552387be7f14cbe2ac6/django/db/models/fields/__init__.py#L504-L522
Field.__reduce__].
The code added in #19635 could be either adjusted to raise a
`RuntimeError` or return another unpickling function that relies on the
`__path__` of the abstract model to retrieve the associated class and call
`_meta.get_field()` on it.
--
Ticket URL: <https://code.djangoproject.com/ticket/25361#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 [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/065.2b837adc27f93c33c0074a35114b7cab%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
