summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorRussell Keith-Magee <russell@keith-magee.com>2010-02-24 14:06:51 +0000
committerRussell Keith-Magee <russell@keith-magee.com>2010-02-24 14:06:51 +0000
commitf7b415869c20ae39180e7b783fabae911a0a0893 (patch)
treee18d7bd42c3b985d3dec15010c4ac803392ba5b2 /docs
parentd33fd127f8f0f7f71e1bc3e7974cebb408e44cea (diff)
[1.1.X] Fixed #12538 -- Added a note that pickles aren't stable during version updates. Thanks to snow0x2d0 for the suggestion.
Backport of r12560 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.1.X@12565 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/models/querysets.txt8
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 85db98c075..75eb8bdb29 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -102,6 +102,14 @@ the query construction and is not part of the public API. However, it is safe
(and fully supported) to pickle and unpickle the attribute's contents as
described here.
+.. admonition:: You can't share pickles between versions
+
+ Pickles of QuerySets are only valid for the version of Django that
+ was used to generate them. If you generate a pickle using Django
+ version N, there is no guarantee that pickle will be readable with
+ Django version N+1. Pickles should not be used as part of a long-term
+ archival strategy.
+
.. _pickle: http://docs.python.org/library/pickle.html
.. _queryset-api: