#4136: NULL fields and Unique keys
-------------------------------------+-------------------------------------
Reporter: David Cramer | Owner:
<dcramer@…> | aashu_dwivedi
Type: Bug | Status: assigned
Component: Forms | Version: 1.3-rc1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by msopacua):
* cc: m.r.sopacua@… (added)
Comment:
Just to throw in my 2 cents here: if this is a general form problem the
answer is not a special widget with a 'NULL' description as users of a
site should not be expected to know the difference, which means one should
be able to describe in the field's init method what the description of the
radio buttons should be, like (..., provided_value="My cat's name",
absent_value="I have no cat").
Also the simplest option is to always insert as NULL if null and unique
are True as there are very few real world cases where an empty value is an
actual valid option. One could also make this case for non-unique but null
fields, however there's no actual distinction between a NULL value and an
empty string in this case.
--
Ticket URL: <https://code.djangoproject.com/ticket/4136#comment:24>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
