Django/django
11
0
Fork 0
Code Pull Requests Projects Releases Activity

[1.7.x] Fixed #5726 -- Documented that inspectdb doesn't detect defaults.

Browse Source 
Backport of 15cafaa565 from master
This commit is contained in:
Tim Graham 2014-08-19 06:14:14 -04:00
parent 5f54752b9d
commit d6c6181f9e
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/ref/django-admin.txt
View File

@ -354,6 +354,11 @@ needed.
``inspectdb`` works with PostgreSQL, MySQL and SQLite. Foreign-key detection ``inspectdb`` works with PostgreSQL, MySQL and SQLite. Foreign-key detection
only works in PostgreSQL and with certain types of MySQL tables. only works in PostgreSQL and with certain types of MySQL tables.
Django doesn't create database defaults when a
:attr:`~django.db.models.Field.default` is specified on a model field.
Similarly, database defaults aren't translated to model field defaults or
detected in any fashion by ``inspectdb``.
By default, ``inspectdb`` creates unmanaged models. That is, ``managed = False`` 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, 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 modification, and deletion. If you do want to allow Django to manage the