diff options
| author | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2009-03-19 09:04:19 +0000 |
|---|---|---|
| committer | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2009-03-19 09:04:19 +0000 |
| commit | 96d5d434fac940aff854c939bef74394fe2c586e (patch) | |
| tree | 748d32667c86d61aebcab6c7f4aa7c7715fc64de /docs/ref | |
| parent | c485e236bd7e5ea40c64b2fe54d85dbb15b2fd39 (diff) | |
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
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/models/options.txt | 4 |
1 files changed, 4 insertions, 0 deletions
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`` ------------------------- |