#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 bmispelon): If the field is not nullable, is there a case where the reverse of `RemoveField` would not fail? If not, the use of "may" is confusing. As for the question about `default`, that's a good point. I haven't tried and it could make the reverse operation "work" in the sense that Django would be able to get back to a valid state but there's no guarantee that your data would be preserved (any non-default values for that column would be gone). -- Ticket URL: <https://code.djangoproject.com/ticket/25917#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 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.e1afc35e6149d334c92a6a8759c7065b%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.