#26739: Backward operation for RemoveField does not allow a default value in
case
the field is not null.
----------------------------+------------------------------------
Reporter: Gagaro | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Comment (by charettes):
It would be great if we could also rely on the transient default of
`AddField` (`preserve_default=False`) if it has been provided.
e.g. default should not be required in this case
{{{#!python
operations = [
AddField('model', 'field', models.TextField(default='foo'),
preserve_default=False),
RemoveField('model', 'field'),
]
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26739#comment:2>
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.3074da24fa4330ce50d8a4c10664b25e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
