From 75d7bb8d4313f83a832a65cc5e9b17b8ccf97fd1 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Tue, 19 Aug 2014 06:14:14 -0400 Subject: [PATCH] [1.6.x] Fixed #5726 -- Documented that inspectdb doesn't detect defaults. Backport of 15cafaa565 from master --- docs/ref/django-admin.txt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt index fe530598cd..06df6e7d65 100644 --- a/docs/ref/django-admin.txt +++ b/docs/ref/django-admin.txt @@ -314,6 +314,11 @@ 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 +: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`` in the model's ``Meta`` class tells Django not to manage each table's creation and deletion. If you do want to allow Django to manage the table's lifecycle,