#4136: Save empty, nullable CharField's as null rather than as an empty string
-------------------------------------+-------------------------------------
Reporter: David Cramer | Owner: Tim
<dcramer@…> | Graham <timograham@…>
Type: New feature | Status: closed
Component: Forms | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
I agree that reopening this ticket isn't appropriate. A new ticket may not
be required -- a PR referencing this ticket would probably be fine,
although I don't think we generally repeat documentation for a superclass
in a subclass.
--
Ticket URL: <https://code.djangoproject.com/ticket/4136#comment:45>
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/090.36c4d465f33f66eb11b7c99950db0b3c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
