To redress the unfortunate situation where one has to try to reverse the
deletion of a non-null field with no specified defaults:
{{{
#!div style="font-size: 80%"
Code highlighting:
{{{#!python
migrations.RemoveField(model_name="child", name="age_at_birth",
reversal_options={"null": True}),
}}}
}}}
A reversal object as such could be added to many of the migrations
constructs. Let me know if this needs clarification.
--
Ticket URL: <https://code.djangoproject.com/ticket/30611>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => closed
* resolution: => duplicate
* version: 1.11 => master
* component: Uncategorized => Migrations
* type: Uncategorized => New feature
Comment:
Duplicate of #23048. Please do not add duplicates of wontfix tickets and
[https://docs.djangoproject.com/en/stable/internals/contributing/triaging-
tickets/#closing-tickets follow triaging guidelines with regards to
wontfix tickets.]
--
Ticket URL: <https://code.djangoproject.com/ticket/30611#comment:1>