From 1a3029b6b4faf400232c38ff70fb74a97b14d1a9 Mon Sep 17 00:00:00 2001 From: Steven Pousty Date: Tue, 16 Jun 2020 17:35:13 -0700 Subject: [PATCH] [3.1.x] Fixed #31743 -- Doc't that managed=False prevents Django from managing tables modifications. Backport of d2c135da4c75079e45661ec609bd72f27dddf2a9 from master --- docs/ref/models/options.txt | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/ref/models/options.txt b/docs/ref/models/options.txt index e1d927b4e5..e45dfee8dd 100644 --- a/docs/ref/models/options.txt +++ b/docs/ref/models/options.txt @@ -157,11 +157,12 @@ Django quotes column and table names behind the scenes. part of a :djadmin:`flush` management command. That is, Django *manages* the database tables' lifecycles. - If ``False``, no database table creation or deletion operations will be - performed for this model. This is useful if the model represents an existing - table or a database view that has been created by some other means. This is - the *only* difference when ``managed=False``. All other aspects of - model handling are exactly the same as normal. This includes + If ``False``, no database table creation, modification, or deletion + operations will be performed for this model. This is useful if the model + represents an existing table or a database view that has been created by + some other means. This is the *only* difference when ``managed=False``. All + other aspects of model handling are exactly the same as normal. This + includes #. Adding an automatic primary key field to the model if you don't declare it. To avoid confusion for later code readers, it's