There could be a discussion about the need of a date type and a time type when a datetime type could also be used in those situations.
But why not define more than 1?
All mmbase types are modeled after java types.
We do not have 'small string' or 'large string' fields (only STRING), or differences between 'images' or 'files' on the abstract datatype level (only BYTE).
If we follow the idea that (abstract) MMBase Types are easily mapped to java types, then aone DAteTime type (java Date class) will be sufficient.
For time/date/datetime differences, you should use guitypes.
Gomez
