From 72793766a7e5218e8b5d7161cc466abfd70a7d46 Mon Sep 17 00:00:00 2001 From: Timo Graham Date: Sat, 31 Dec 2011 15:30:22 +0000 Subject: [PATCH] Fixed #640 - Documented that changing order_with_respect_to requires a schema change; thanks fcurella and poirier for the draft patches. git-svn-id: http://code.djangoproject.com/svn/django/trunk@17316 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 1303fbcb84..d4c7df1b7a 100644 --- a/docs/ref/models/options.txt +++ b/docs/ref/models/options.txt @@ -176,6 +176,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`` ------------