#21430: Raise explicit error when unpickling QuerySet from incompatible version
-------------------------------------+-------------------------------------
Reporter: FunkyBob | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.6
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by akaariai):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I think this is a good idea. We should invent a new exception type
UnsupportedUnpickleException or something like that.
The implementation doesn't need to be more complicated than adding version
= django's major version to the pickled state in `__getstate__` and then
checking that the version is compatible in `__setstate__`. For first try
we should just raise error if versions differ, later on we might want to
try to actually recover from pickling errors. Unfortunately Query and all
that it depends on seems to be way too complex to successfully do cross-
version unpickling.
--
Ticket URL: <https://code.djangoproject.com/ticket/21430#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/066.b5cbd7639ff886a73087e40d6bec6856%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
