#31278: Schema Editor Action: Pull Field Up
-------------------------------------+-------------------------------------
Reporter: awiebe | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 3.0
Severity: Normal | Resolution: wontfix
Keywords: pullup schemaeditor | Triage Stage:
runpython refactor inheritance | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => wontfix
Comment:
I think this kind of composite operation is out-of-scope for the core
framework.
What you describe sounds right: create the new field, do a data migration,
delete the old field.
But I don't think we'd ship operations to do that for you.
I might say yes to a documentation example, but, beyond basics (and moving
to a custom user model) I don't see that we catalogue various migration
scenarios.
It would make a good blog topic I think.
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/31278#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/064.2fc4044371274244541edf95d34c6ef8%40djangoproject.com.
