#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
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
I also think that `--name` should not be ignored when `--update` is used
but updating the name of the updated migration to follow the usual
operation fragment stitching otherwise seems like a expected default.
Whether or not we we should add an option not to perform optimization or
disable operation fragment usage for migration name entirely seems like
distinct feature requests.
--
Ticket URL: <https://code.djangoproject.com/ticket/34568#comment:8>
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/0107018825b61cac-a574d611-feeb-4d1c-8ec2-28c94a252a6b-000000%40eu-central-1.amazonses.com.
