From f7b415869c20ae39180e7b783fabae911a0a0893 Mon Sep 17 00:00:00 2001 From: Russell Keith-Magee Date: Wed, 24 Feb 2010 14:06:51 +0000 Subject: [PATCH] [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 --- docs/ref/models/querysets.txt | 8 ++++++++ 1 file changed, 8 insertions(+) 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: