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
It seems like there is an issue when dates are saved (on the production server at least). The created date is being saved in MST but the modified date is being saved in UTC. This might be because the MySQL server is configured to use MST but laravel is configured to use UTC. The created_at column is updated by using a default value in the database where updated_at is actually generated by Laravel.
This might be a common / known issue in Laravel, I think it would be worth looking in the documentation or Laravel support forums.
The text was updated successfully, but these errors were encountered:
You can add the following key to your mysql connection in the config:
'options' => array(
\PDO::MYSQL_ATTR_INIT_COMMAND => 'SET time_zone = '+00:00''
)
This example sets your PDO database connection to UTC. So if the database itself runs in another timezone, your app wil always get the timestamps as UTC.
It seems like there is an issue when dates are saved (on the production server at least). The created date is being saved in MST but the modified date is being saved in UTC. This might be because the MySQL server is configured to use MST but laravel is configured to use UTC. The
created_at
column is updated by using a default value in the database whereupdated_at
is actually generated by Laravel.This might be a common / known issue in Laravel, I think it would be worth looking in the documentation or Laravel support forums.
The text was updated successfully, but these errors were encountered: