#25917: Confusing sentence in RemoveField's documentation
--------------------------------------+------------------------------------
Reporter: bmispelon | Owner:
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by kaifeldhoff):
It seems like everything is pretty clear here and this ticket could be
finished. My suggestion for the respective section in the docs is below.
As I am not a native speaker, I appreciate feedback.
By the time everything is fine, I'd like to add this to the docs being my
first ticket.
''Bear in mind that when reversed this is actually adding a field to a
model. To make this possible, Django needs a default value to populate the
recreated empty column. This is only possible for a field that is nullable
or has a defined default value.
On the other hand if the field is not nullable and does not have a default
value, this operation is irreversible (apart from any data loss, which of
course is irreversible).''
--
Ticket URL: <https://code.djangoproject.com/ticket/25917#comment:7>
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/067.7e7f164cc3a85db0794fa3a3e082ef75%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
