From 9b7ba8af1b4ddb539cd69cbec9645cd873db7624 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Tue, 25 Mar 2014 10:17:23 -0400 Subject: Fixed #22322 -- Fixed incorrect explanation of what managed=False does. refs #14305. Thanks Adrian Klaver for the report. --- docs/ref/django-admin.txt | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) (limited to 'docs/ref') diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt index 275d7e53c1..8f4a832986 100644 --- a/docs/ref/django-admin.txt +++ b/docs/ref/django-admin.txt @@ -347,15 +347,12 @@ needed. ``inspectdb`` works with PostgreSQL, MySQL and SQLite. Foreign-key detection only works in PostgreSQL and with certain types of MySQL tables. -If your plan is that your Django application(s) modify data (i.e. edit, remove -records and create new ones) in the existing database tables corresponding to -any of the introspected models then one of the manual review and edit steps -you need to perform on the resulting ``models.py`` file is to change the -Python declaration of each one of these models to specify it is a -:attr:`managed ` one. - -This serves as an explicit opt-in to give your nascent Django project write -access to your precious data on a model by model basis. +By default, ``inspectdb`` creates unmanaged models. That is, ``managed = False`` +in the model's ``Meta`` class tells Django not to manage each table's creation, +modification, and deletion. If you do want to allow Django to manage the +table's lifecycle, you'll need to change the +:attr:`~django.db.models.Options.managed` option to ``True`` (or simply remove +it because ``True`` is its default value). The :djadminopt:`--database` option may be used to specify the database to introspect. -- cgit v1.3