#31047: Empty models.TextField being incorrectly saved as empty string -------------------------------------+------------------------------------- Reporter: Ebenezer | Owner: nobody Hailemariam | Type: Bug | Status: new Component: Database layer | Version: 2.2 (models, ORM) | 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 inoks): I think empty HTML textarea send the value as an empty string instead of null/None. The only solution may be to set `disabled` attribute for the textarea. In that case, the value for that field will not be submitted to the server and `null` should be saved into the DB instead of the empty string. -- Ticket URL: <https://code.djangoproject.com/ticket/31047#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 view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/062.d0ba739b07aef158e484117c08dfb7fe%40djangoproject.com.