summaryrefslogtreecommitdiff
path: root/docs/ref/models
diff options
context:
space:
mode:
authorRussell Keith-Magee <russell@keith-magee.com>2010-02-24 13:56:19 +0000
committerRussell Keith-Magee <russell@keith-magee.com>2010-02-24 13:56:19 +0000
commitd7927377703bb2b99702907c448e2195f4801687 (patch)
treed3c0c1d0c21cdf13835e35400ffc0e66bab33461 /docs/ref/models
parent841210b308ae76ed8748c76f54b7d9343c8140a1 (diff)
Fixed #12538 -- Added a note that pickles aren't stable during version updates. Thanks to snow0x2d0 for the suggestion.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@12560 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/ref/models')
-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 f0eceb130d..b334240b6c 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -106,6 +106,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: