#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 David Sanders):
This is my first time using `--update` and here are a few other
observations which could indicate that it requires broader discussion:
- It doesn't utilise the `--name` argument so it's impossible to
customise the name during `--update`
- 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 non-null update into
the migration but `--update` optimizes this into a single step.
Perhaps `--update` requires a rethink?
--
Ticket URL: <https://code.djangoproject.com/ticket/34568#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/0107018823ff07dc-ac9afdde-dbf4-465b-8eaa-7dcbed20e3a8-000000%40eu-central-1.amazonses.com.
