Opened 2 years ago
Last modified 2 years ago
#34052 closed Bug
migrate --check still emits signals if database is up to date — at Version 6
Reported by: | Jacob Walls | Owned by: | JunKi Yoon |
---|---|---|---|
Component: | Migrations | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description (last modified by )
pre_migrate
and post_migrate
signals are emitted for migrate --check
, but only if the database is up-to-date.
A related side effect is that the logs also look like a like a real run, as it says "Operations to perform:" and "Running migrations:". The last sentence clarifies that nothing has been applied, but there is still the potential for a half-second of "what have I just done?".
% python manage.py migrate --check Operations to perform: Apply all migrations: admin, auth, contenttypes, sessions, social_django Running migrations: No migrations to apply.
Change History (6)
comment:1 by , 2 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 2 years ago
comment:3 by , 2 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:5 by , 2 years ago
Needs tests: | set |
---|---|
Patch needs improvement: | set |
comment:6 by , 2 years ago
Description: | modified (diff) |
---|
Note:
See TracTickets
for help on using tickets.
Replying to Jacob Walls:
Can I try this ticket?