#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
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: new => closed
* resolution: => fixed
Comment:
Hi Matt,
Please submit a new ticket suggesting your documentation adjustments
instead of reopening this one to avoid notifying the large number of
people that CCed over the past 10 years.
Linking to this ticket by number (e.g. #4136) should be enough to provide
context in your report.
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/4136#comment:44>
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.c5bd0e46c9c4ad5122286e33eb999d22%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
