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
We recently switched to calulating token expirey datetime’s to store as UTC. When the doctrine adapter loads the datetime back from db (and using mysql which doesn’t store the tz in the db) the date i get back are reconsituted in the local tz. Would you recommend the application should also run in UTC? Or the database with [mysqld] default-time-zone='+00:00’ Tokens (especially authorization code) are expired too soon… Should definitely switch the doctrine xml datetime to datetimetz but (as said) doesn’t help when using mysql...
We recently switched to calulating token expirey datetime’s to store as UTC. When the doctrine adapter loads the datetime back from db (and using mysql which doesn’t store the tz in the db) the date i get back are reconsituted in the local tz. Would you recommend the application should also run in UTC? Or the database with [mysqld] default-time-zone='+00:00’ Tokens (especially authorization code) are expired too soon… Should definitely switch the doctrine xml datetime to datetimetz but (as said) doesn’t help when using mysql...
Reading this http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/cookbook/working-with-datetime.html#default-timezone-gotcha I think manually setting the date_default_timezone_set to utc before each read and then back its original is the only correct way.
The text was updated successfully, but these errors were encountered: