#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):
@felix read through that PR, I'm assuming your point about ending up with
a name that doesn't match the operations is referring to not being able to
tell the difference between a custom name and an auto gen'd name. Here's
my response:
- It's a fair point. Trying to determine custom names is too complex and
shouldn't be done.
- In my anecdotal experience we (myself and colleagues) rarely use the
auto gen'd name. An option to `--keep-name` sounds nice to me with the
default to *not keep*.
- If not, then at the very least supplying `--name` should raise an
exception or honour the name. It definitely shouldn't do *nothing*. My
preference is to honour `--name` 😊
Can we get Simon's take as well since he was part of the thread?
I still think something should change because it's not even fancy… I'd say
that turning off optimisations is harder than this.
--
Ticket URL: <https://code.djangoproject.com/ticket/34568#comment:4>
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/01070188244dbff5-20f948f8-e11b-4d25-b89c-9ea6d97f23b4-000000%40eu-central-1.amazonses.com.
