From 96d5d434fac940aff854c939bef74394fe2c586e Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Thu, 19 Mar 2009 09:04:19 +0000 Subject: Added some documentation explaining "managed=False" vs. "proxy=True". These features look similar, but they're not identical. They can't be merged into one (without requiring at least two Meta parameters anyway), so we've made them have APIs that match their natural use-cases most easily. Anyway, the documentation explains both the details and gives some simple to follow rules. git-svn-id: http://code.djangoproject.com/svn/django/trunk@10089 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/models/options.txt | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'docs/ref') diff --git a/docs/ref/models/options.txt b/docs/ref/models/options.txt index 60a3064dff..a0ef5b3d4b 100644 --- a/docs/ref/models/options.txt +++ b/docs/ref/models/options.txt @@ -99,6 +99,10 @@ attribute. For tests involving models with ``managed=False``, it's up to you to ensure the correct tables are created as part of the test setup. +If you're interested in changing the Python-level behaviour of a model class, +you *could* use ``managed=True`` and create a copy of an existing model. +However, there's a better approach for that situation: :ref:`proxy-models`. + ``order_with_respect_to`` ------------------------- -- cgit v1.3