#3408: DateField, TimeField, and DateTimeField to_python() handles null values
incorrectly
--------------------------------------------+-------------------------------
Reporter: Brantley <[EMAIL PROTECTED]> | Owner: adrian
Status: new | Component: Database wrapper
Version: SVN | Keywords: to_python,
validation, model
Stage: Unreviewed | Has_patch: 1
--------------------------------------------+-------------------------------
DateField, TimeField, and DateTimeField all throw errors incorrectly
during serialization and validation when they have a null value even if
the model specifies that a null value is acceptable. The patch included
simply checks for None as the value, then either returns that value, or
raises an appropriate validation error if the field cannot be null.
--
Ticket URL: <http://code.djangoproject.com/ticket/3408>
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
-~----------~----~----~----~------~----~------~--~---
