summaryrefslogtreecommitdiff
path: root/docs/ref
diff options
context:
space:
mode:
authorThomas Güttler <guettliml.github@thomas-guettler.de>2016-10-19 11:37:04 +0200
committerTim Graham <timograham@gmail.com>2016-10-26 11:09:06 -0400
commit72d174bc4e24eaf2c75bd2d411cec3cb3ad282f9 (patch)
tree4c62ca6ca8fac70af6d4621a6fe7e0d9b607feed /docs/ref
parent736f7e7ed7d04cfb9032636b5b65cba26ec7d6db (diff)
[1.10.x] Clarified when the post_migrate signal is sent during migrate.
Backport of 7cdc2015e37e7fd9a0e5ff7315a61086c2aad803 from master
Diffstat (limited to 'docs/ref')
-rw-r--r--docs/ref/signals.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/ref/signals.txt b/docs/ref/signals.txt
index cc0567bc3b..f23bb9eb8c 100644
--- a/docs/ref/signals.txt
+++ b/docs/ref/signals.txt
@@ -429,13 +429,13 @@ Arguments sent with this signal:
.. data:: django.db.models.signals.post_migrate
:module:
-Sent by the :djadmin:`migrate` command after it installs an application, and the
-:djadmin:`flush` command. It's not emitted for applications that lack a
+Sent at the end of the :djadmin:`migrate` (even if no migrations are run) and
+:djadmin:`flush` commands. It's not emitted for applications that lack a
``models`` module.
-It is important that handlers of this signal perform idempotent changes (e.g.
-no database alterations) as this may cause the :djadmin:`flush` management
-command to fail if it also ran during the :djadmin:`migrate` command.
+Handlers of this signal must not perform database schema alterations as doing
+so may cause the :djadmin:`flush` command to fail if it runs during the
+:djadmin:`migrate` command.
Arguments sent with this signal: