#24086: No pre_migrate signal is emitted if rolling back the migration history
------------------------------------+--------------------------------------
Reporter: andrewhayes1979 | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Normal | Resolution: worksforme
Keywords: pre_migrate signal | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+--------------------------------------
Changes (by timgraham):
* status: new => closed
* resolution: => worksforme
Comment:
I couldn't reproduce the lack of the `pre_migrate` signal as you describe.
Here's a test for Django's test suite that passes. I also tested manually
by using the tutorial app and running `python manage.py migrate polls
0001` after generating a second migration. I put a print statement in
`emit_pre_migrate_signal()` and verified it was executed. Please reopen if
I've missed something or if you can provide a failing test.
Regarding your aside (please create a separate ticket in the future), a
similar feature request is tracked in #24100.
--
Ticket URL: <https://code.djangoproject.com/ticket/24086#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.5883222c499b8362702b3f613a6540ed%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
