#34568: makemigrations --update changes the name of custom migration name
-------------------------------------+-------------------------------------
Reporter: David Sanders | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution:
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):
* cc: David Wobrock (added)
Comment:
I think you're expecting too much from `--update` was intended to be an
option for updating recently developed changes and don't do anything
fancier. Please check the discussion in
[https://github.com/django/django/pull/15669 PR].
> My opinion is that it shouldn't as it violates the principle of least
astonishment even though the --name argument wasn't supplied.
We could document this behavior, but IMO it shouldn't be changed.
> It'd be nice to provide --no-optimize option to --update, here's my use-
case: 3-step non-null field addition. After doing nullable step 1,
elidable data migration step 2, I want to merge the step 3 non-null update
into the migration but --update optimizes this into a single step.
It's probably worth adding 🤔
--
Ticket URL: <https://code.djangoproject.com/ticket/34568#comment:3>
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/01070188240a88c0-1eda3f44-cc6d-4935-9e12-4803d139826d-000000%40eu-central-1.amazonses.com.
