Clarified when the post_migrate signal is sent during migrate.

This commit is contained in:
Thomas Güttler 2016-10-19 11:37:04 +02:00 committed by Tim Graham
parent f3ea0c4bbd
commit 7cdc2015e3
1 changed files with 5 additions and 5 deletions

View File

@ -429,13 +429,13 @@ Arguments sent with this signal:
.. data:: django.db.models.signals.post_migrate .. data:: django.db.models.signals.post_migrate
:module: :module:
Sent by the :djadmin:`migrate` command after it installs an application, and the Sent at the end of the :djadmin:`migrate` (even if no migrations are run) and
:djadmin:`flush` command. It's not emitted for applications that lack a :djadmin:`flush` commands. It's not emitted for applications that lack a
``models`` module. ``models`` module.
It is important that handlers of this signal perform idempotent changes (e.g. Handlers of this signal must not perform database schema alterations as doing
no database alterations) as this may cause the :djadmin:`flush` management so may cause the :djadmin:`flush` command to fail if it runs during the
command to fail if it also ran during the :djadmin:`migrate` command. :djadmin:`migrate` command.
Arguments sent with this signal: Arguments sent with this signal: