#25917: Confusing sentence in RemoveField's documentation
-------------------------------------+-------------------------------------
Reporter: bmispelon | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by rfleschenberg):
As I understand it, the sentence means this: if the field is not nullable,
the reverse of RemoveField (adding a field) may fail, because Django does
not know which data to add for existing rows.
Apart from that, the forward operation (removing the field) is of course
never reversible in so far as it deletes the data in the field.
Question: would RemoveField be reversible if the field has a default
value?
--
Ticket URL: <https://code.djangoproject.com/ticket/25917#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.3c799351359ccfd45a9315a116389590%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
