#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: new
Component: Forms | Version: master
Severity: Normal | Resolution:
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 Matt Braymer-Hayes):
* status: closed => new
* resolution: fixed =>
Comment:
Hi folks, question: Do these changes also impact `models.CharField`
subclasses (`CommaSeparatedIntegerField`, `EmailField`, `SlugField`, and
`URLField`) and `forms.CharField` subclasses (`RegexField`, `EmailField`,
`URLField`, `GenericIPAddressField`, `SlugField`, and `UUIDField`)? If so,
the docstrings and documentation for each of the `forms.CharField`
subclasses should be updated. I'm happy to make a PR, if this is the case.
--
Ticket URL: <https://code.djangoproject.com/ticket/4136#comment:43>
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.d33e094e9b5143b908967bf98663a976%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
