#32184: `manage.py migrate --noinput` should not delete stale modules
-------------------------------------+-------------------------------------
Reporter: uy-rrodriguez | Owner: nobody
Type: Bug | Status: closed
Component: Core (Management | Version: 2.2
commands) |
Severity: Normal | Resolution: wontfix
Keywords: migrate, no-input, | Triage Stage:
noinput, management | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => wontfix
Comment:
Hi. Thanks for the report. I am going to say wontfix here initially, as it
sounds to me like expected behaviour.
`migrate` synchronizes the database state with the current set of models
and migrations — both adding and removing — and `--noinput` says ''Don't
ask me for confirmation''. If you're in any doubt as to the exact
operations that will be performed you should use `--plan` to verify
beforehand.
I hope that makes sense.
However, if you want to follow up with an exact example (with a sample
project preferably) of where an operation is performed that you think it
should not be I am happy to look at that to double check here.
Thanks again.
--
Ticket URL: <https://code.djangoproject.com/ticket/32184#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.ea5266b6739aa6bad1872c0514076f7e%40djangoproject.com.
