From 7cdc2015e37e7fd9a0e5ff7315a61086c2aad803 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20G=C3=BCttler?= Date: Wed, 19 Oct 2016 11:37:04 +0200 Subject: [PATCH] Clarified when the post_migrate signal is sent during migrate. --- docs/ref/signals.txt | 10 +++++----- 1 file 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: