#4136: NULL fields and Unique keys
------------------------------------------------+---------------------------
Reporter: David Cramer <[EMAIL PROTECTED]> | Owner: nobody
Status: new | Component: Admin
interface
Version: 0.96 | Resolution:
Keywords: | Stage:
Accepted
Has_patch: 0 | Needs_docs: 1
Needs_tests: 0 | Needs_better_patch: 0
------------------------------------------------+---------------------------
Changes (by SmileyChris):
* component: Database wrapper => Admin interface
Comment:
This seems more of an admin problem than a db wrapper problem. The db
handles it fine (as far as I know) if you actually set the value to be
`None`, it is just the fact that the admin can't tell (or accurately
display) the difference between a blank string and null.
I think newforms-admin should have a special `NullCharField` widget for db
`CharField`s which have `null=True` with two radio options, the first with
a label of "None" and the second with the text box. This way, you can make
the differentiation between a null and blank string.
--
Ticket URL: <http://code.djangoproject.com/ticket/4136#comment:7>
Django Code <http://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 this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
