#8898: `required` validation bypassed when using `DateTimeField` with
`SplitDateTimeWidget`.
---------------------------------------------+------------------------------
Reporter: mrmachine | Owner: nobody
Status: new | Milestone:
Component: Forms | Version: SVN
Resolution: | Keywords: DateTimeField
SplitDateTimeWidget
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Changes (by jacob):
* stage: Accepted => Design decision needed
Comment:
Replying to [comment:8 mrmachine]:
> It's currently impossible to use an optional DateTimeField in the Django
admin, with an exception being generated if no value is specified.
That doesn't seem to be true; this works fine for me:
{{{
class Bug8898(models.Model):
timestamp = models.DateTimeField(blank=True, null=True)
}}}
I'm thinking there's not a bug here -- as Karen said, `SplitDateTimeField`
is the right choice here -- but if there is can you please clarify how (if
at all) this breaks forms and/or the admin?
--
Ticket URL: <http://code.djangoproject.com/ticket/8898#comment:10>
Django <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
-~----------~----~----~----~------~----~------~--~---
