#32387: More efficiant migration management
-----------------------------+--------------------------------------
Reporter: francois90 | Owner: nobody
Type: New feature | Status: closed
Component: Migrations | Version: 3.1
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => wontfix
Comment:
Thanks for this proposition, however I don't see why you need a special
built-in workflow to do this. `makemigrations` already supports the
`--name` option, so you can name uncommitted migrations in a different way
and do this exactly as described. Most of this flow is outside of Django.
I don't see a reason to add a new option and especially encourage it.
--
Ticket URL: <https://code.djangoproject.com/ticket/32387#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.81b87bc62e0f48cae4eacbbfb9213152%40djangoproject.com.
