#33466: Schema Modification using Migrations
-------------------------------------+-------------------------------------
Reporter: kenprogrammer | Owner: nobody
Type: New feature | Status: closed
Component: Migrations | Version: 4.0
Severity: Normal | Resolution: invalid
Keywords: migrations,column | Triage Stage:
after,mysql | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
Comment:
Does the order in which the columns are added to the table really matter
to you? I cannot image any scenario where this could be an issue. You can
always do this in 4 steps:
- create a new model with a temporary name,
- copy data between models,
- drop old model,
- rename new model to the target name.
--
Ticket URL: <https://code.djangoproject.com/ticket/33466#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.642be4e8d73458f22c50e239ddac789b%40djangoproject.com.
