You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we serialize the date time using Frequency::SERIALIZED_DATETIME_FORMAT which includes the timezone offset P. Timezone offset can change over time due to DST changes for example and would end up with wrong timezone offset in the database as it's shifted back/forward by 1 hour. Also, date time deserialized with this format would return timezone offset +00:00 instead of the abbreviated timezone name like UTC, when using DateTimeZone::getName().
The text was updated successfully, but these errors were encountered:
Currently we serialize the date time using
Frequency::SERIALIZED_DATETIME_FORMAT
which includes the timezone offsetP
. Timezone offset can change over time due toDST
changes for example and would end up with wrong timezone offset in the database as it's shifted back/forward by 1 hour. Also, date time deserialized with this format would return timezone offset+00:00
instead of the abbreviated timezone name likeUTC
, when usingDateTimeZone::getName()
.The text was updated successfully, but these errors were encountered: