#23048: Add the ability to make RemoveField reversible for non-null fields
--------------------------------+------------------------------------
Reporter: harrislapiroff | Owner: nobody
Type: New feature | Status: closed
Component: Migrations | Version: 1.7-rc-1
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+------------------------------------
Changes (by andrewgodwin):
* status: new => closed
* resolution: => wontfix
Comment:
Adding a default on the model field or on the field in the migration
should solve this, as it'll be able to populate the new field with that
when it makes it. The only other option is to prompt people for a default
every time they *remove* a not null field, which really confused people in
South, so let's not do that.
Closing as WONTFIX, as the solution is a simple edit to the migration.
--
Ticket URL: <https://code.djangoproject.com/ticket/23048#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/072.a07e0b88e01006eaa03a8e1daadc4ec3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
