#4136: NULL fields and Unique keys
-------------------------------------+-------------------------------------
Reporter: David Cramer | Owner: nobody
<dcramer@…> | Status: new
Type: Bug | Version: 1.3-rc1
Component: Forms | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 1
Has patch: 1 | Patch needs improvement: 1
Needs tests: 1 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
Maybe a new form field init argument is needed: blank_as_none? Better name
welcome. I don't see any other way forward. Currently it is impossible for
the form layer to know if the given empty value should be treated as "" or
None.
Maybe we need a matching model field init argument, too. Setting
null=True, blank=True can not be translated to blank_as_none, as this
would be backwards incompatible.
--
Ticket URL: <https://code.djangoproject.com/ticket/4136#comment:21>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
