From: Brian Lloyd [EMAIL PROTECTED]
I agree. I'd specify this by saying:
o An empty string sent from a browser for an optional_date
field is interpreted as a null (not specified) value
o The internal representation of an optional_date (the
value you find in the REQUEST after
From: Brian Lloyd [EMAIL PROTECTED]
Sure. The property forms just need to do the equivalent
of:
dtml-if theDate
dtml-var theDate fmt=somthing
/dtml-if
I know that this is a style issue to some
Yeah, it's not the most neat solution. But it works...
So, to summarize:
The new field type,
http://collector.zope.org/Zope/30
What are people take on empty dates?
snip
This is a problem, because we need to be able to have empty dates. Also,
enetering something magick (like None, or 1980/0/0 isn't usable.
We fix this
with this simple patch, which so far has caused us no
From: Brian Lloyd [EMAIL PROTECTED]
I propose that we could add a new field type with a name
like optional_date. The converter handler for that type could
handle an empty field in whatever way we feel is reasonable,
without breaking existing applications. (Let the fight over
reasonable
I propose that we could add a new field type with a name
like optional_date. The converter handler for that type could
handle an empty field in whatever way we feel is reasonable,
without breaking existing applications. (Let the fight over
reasonable begin! :^)
That's fine by me. And
