[2.1.x] Removed docs for obsolete limitations of inspectdb.
Backport of 31edb106b5
from master.
This commit is contained in:
parent
f0759305d0
commit
95c2ce678f
|
@ -385,13 +385,6 @@ you run it, you'll want to look over the generated models yourself to make
|
||||||
customizations. In particular, you'll need to rearrange models' order, so that
|
customizations. In particular, you'll need to rearrange models' order, so that
|
||||||
models that refer to other models are ordered properly.
|
models that refer to other models are ordered properly.
|
||||||
|
|
||||||
Primary keys are automatically introspected for PostgreSQL, MySQL and
|
|
||||||
SQLite, in which case Django puts in the ``primary_key=True`` where
|
|
||||||
needed.
|
|
||||||
|
|
||||||
``inspectdb`` works with PostgreSQL, MySQL and SQLite. Foreign-key detection
|
|
||||||
only works in PostgreSQL and with certain types of MySQL tables.
|
|
||||||
|
|
||||||
Django doesn't create database defaults when a
|
Django doesn't create database defaults when a
|
||||||
:attr:`~django.db.models.Field.default` is specified on a model field.
|
:attr:`~django.db.models.Field.default` is specified on a model field.
|
||||||
Similarly, database defaults aren't translated to model field defaults or
|
Similarly, database defaults aren't translated to model field defaults or
|
||||||
|
|
Loading…
Reference in New Issue