mirror of
https://github.com/django/django.git
synced 2025-05-28 01:36:29 +00:00
[1.10.x] Clarified when the post_migrate signal is sent during migrate.
Backport of 7cdc2015e37e7fd9a0e5ff7315a61086c2aad803 from master
This commit is contained in:
parent
736f7e7ed7
commit
72d174bc4e
@ -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:
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user