#24870: Create --update flag for makemigrations management command, mimicking
South's one.
-------------------------------------+-------------------------------------
Reporter: Israel Saeta Pérez | Owner: David
| Wobrock
Type: New feature | Status: assigned
Component: Migrations | Version: dev
Severity: Normal | Resolution:
Keywords: migrations, south | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by David Wobrock):
* cc: David Wobrock (added)
* owner: nobody => David Wobrock
* has_patch: 0 => 1
* status: new => assigned
Comment:
Hello,
I tried to tackle this ticket as I believe it would still be a pretty
useful addition to `makemigrations`.
During development, I often see developers struggle with the manual steps
to re-generate a migration while they are still iterating on their
approach.
Here is the approach I've taken
https://github.com/django/django/pull/15669
I tried to keep the implementation rather straightforward.
The main drawback I see is that it will add a new edge case when one
updates a migration that has already been applied. This will create a bit
of confusion, as it will become more tedious to undo the updated
migration, since the reverse operations will try to undo things that
weren't initially applied.
--
Ticket URL: <https://code.djangoproject.com/ticket/24870#comment:5>
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/010701809b0c8157-147f23a6-ea22-460f-9810-d6fb098e1d13-000000%40eu-central-1.amazonses.com.