#24375: Add ability to mark migration as "part of initial" in Migration
---------------------------------+------------------------------------
Reporter: haeric | Owner: akulakov
Type: New feature | Status: assigned
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: fake migrations | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by haeric):
Yes, great idea, 'initial' is an even better solution to this problem for
all the reasons you mentioned. Neat bonus to get rid of the magic
detection for initial migration!
For my particular problem I ended up making a custom AddField that simply
does nothing if the field is already there. But an `initial` would
certainly solve it, in my mind, more elegantly.
--
Ticket URL: <https://code.djangoproject.com/ticket/24375#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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.d66a75a7af1b3d2870a67e2561722c17%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
