#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 |
---------------------------------------------+------------------------------
Comment (by kmtracey):
Also related: #9721. That one wants to mix together the
!SplitDateTimeWidget with a !DateTimeField in order to allow for an
optional time component. Perhaps that is why !DateTimeField was given
some support for getting input from a !SplitDateTimeWidget in the first
place? If so I think a better approach could be to add support for that
kind of thing to the !SplitDateTimeField/!SplitDateTimeWidget combo rather
than trying to mix a split widget with a non-split field.
--
Ticket URL: <http://code.djangoproject.com/ticket/8898#comment:14>
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
