Task #55953: Repair and streamline ValueObject support
more suitable ValueObject hash creation for DateTime cases
currently, DateTime objects are only represented by their ("unix-") Timestamp, which may result in unpredictable behavior when server time (zone) or Daylight Saving Time changes.
An RFC850 formatted date seems to be more appropriate, it says e.g.
Monday, 15-Aug-05 15:52:01 UTC or
Monday, 21-May-12 14:19:41 CEST (note the s in CEST that indicates summer time).
Otherwise, both, for example, British Summer Time (+01:00) and Central European Time (non-summer) would be +01:00, but representing very different actual Dates.