#4136: NULL fields and Unique keys
------------------------------------------------+---------------------------
Reporter: David Cramer <[EMAIL PROTECTED]> | Owner: adrian
Status: new | Component:
Database wrapper
Version: 0.96 | Resolution:
Keywords: | Stage:
Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------------------------+---------------------------
Comment (by ubernostrum):
Hm. The problem here is that fields which -- in Python -- reduce to a
string value have null input stored as empty strings instead of as `NULL`
(this is mentioned in [http://www.djangoproject.com/documentation/model-
api/#null the model docs]), and with good reason; as the docs point out,
allowing both `NULL` and an empty string creates ambiguity. I'm not sure
what the best solution is here in the face of a nullable but unique field
which holds a string.
--
Ticket URL: <http://code.djangoproject.com/ticket/4136#comment:3>
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
-~----------~----~----~----~------~----~------~--~---
