Bug #37357

Task #55953: Repair and streamline ValueObject support

more suitable ValueObject hash creation for DateTime cases

Added by Adrian Föder over 9 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Should have
Assignee:
Category:
Persistence
Target version:
-
Start date:
2012-05-21
Due date:
% Done:

100%

Estimated time:
PHP Version:
Has patch:
Yes
Complexity:
easy

Description

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.

Also available in: Atom PDF