Bug #37357

more suitable ValueObject hash creation for DateTime cases

Added by Adrian Föder about 1 year ago. Updated 2 days ago.

Status:Under Review Start date:2012-05-21
Priority:Should have Due date:
Assignee:Adrian Föder % Done:

0%
Category:Persistence
Target version:-
PHP Version: Complexity:easy
Has patch:Yes FLOW3 version affected:(any)
Votes: 0

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.

History

#1
Updated by Gerrit Code Review about 1 year ago

  • Status changed from New to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/11368

#2
Updated by Karsten Dambekalns about 1 year ago

  • Target version changed from 1.1 beta 2 to 2.0 beta 1

#3
Updated by Gerrit Code Review 10 months ago

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/11368

#4
Updated by Karsten Dambekalns 5 months ago

  • Target version changed from 2.0 beta 1 to 2.1
  • FLOW3 version affected changed from Git master to (any)

#5
Updated by Gerrit Code Review 5 months ago

Patch set 3 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11368

#6
Updated by Gerrit Code Review 5 months ago

Patch set 4 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11368

#7
Updated by Robert Lemke 2 days ago

  • Target version deleted (2.1)

Also available in: Atom PDF