#12538: Removal (rename) of BaseQuery in SVN version causes ImportError for
previously pickled Querysets
------------------------------------+---------------------------------------
Reporter: snow0x2d0 | Owner: nobody
Status: new | Milestone: 1.2
Component: Documentation | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by russellm):
* stage: Unreviewed => Accepted
* component: Database layer (models, ORM) => Documentation
* milestone: => 1.2
Comment:
There's almost no way that we could protect against this sort of problem.
Any change to the internals of a class like Query - which *will* happen
between Django versions - will inevitably lead to unpickling problems, as
the old class won't be compatible with the new class. Even if we hadn't
renamed BaseQuery->Query, this would have still been a problem due to the
massive internal refactoring of the Query class itself.
A documentation note to the effect of "pickles won't survive a version
update" on [http://docs.djangoproject.com/en/dev/ref/models/querysets/#id2
the queryset pickling docs] is about the best we can do here.
--
Ticket URL: <http://code.djangoproject.com/ticket/12538#comment:3>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
