#21430: Raise explicit error when unpickling QuerySet from incompatible version
-------------------------------------+-------------------------------------
Reporter: FunkyBob | Owner:
Type: New feature | anubhav9042
Component: Database layer | Status: assigned
(models, ORM) | Version: master
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 anubhav9042):
Replying to [comment:2 akaariai]:
> By the way, I don't think we should leave this to just QuerySet. I know
that at least Model unpickling can have this same issue. But for model
unpickling we might be able to actually do cross-version conversions in
`__getstate__()` and `__setstate__()`. Again, first try lets just throw an
error.
Can you please comment out your thoughts regarding cross-version
conversion. I mean if you have thought of any way to pickle `Models` than
the normal way or some other startegy.
--
Ticket URL: <https://code.djangoproject.com/ticket/21430#comment:7>
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/066.9f641f3ccbba701522b984df9bcc3865%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
