From 7bee6b451afd80f98aa8c720ec2d61177f0674b5 Mon Sep 17 00:00:00 2001 From: Timo Graham Date: Sat, 31 Dec 2011 15:30:41 +0000 Subject: [PATCH] [1.3.X] Fixed #640 - Documented that changing order_with_respect_to requires a schema change; thanks fcurella and poirier for the draft patches. Backport of r17316 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.3.X@17317 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/models/options.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/ref/models/options.txt b/docs/ref/models/options.txt index aae90d0b6a..c1beab03ec 100644 --- a/docs/ref/models/options.txt +++ b/docs/ref/models/options.txt @@ -166,6 +166,13 @@ Django quotes column and table names behind the scenes. >>> answer.get_previous_in_order() +.. admonition:: Changing order_with_respect_to + + ``order_with_respect_to`` adds an additional field/database column + named ``_order``, so be sure to handle that as you would any other + change to your models if you add or change ``order_with_respect_to`` + after your initial :djadmin:`syncdb`. + ``ordering`` ------------