Most of the currently available functions/extensions/behaviors directly or indirectly use timestamps to perform "format" and "timezone" conversions. This creates problems for dates falling outside the timestamp range; and the two forms of conversions must often be done in separate processes. However, by using php's DateTime class (instead of timestamps), we can do both conversions on a single DateTime object (only 2 lines of code) for date, time, timestamp and datetime types - while php takes care of nightmares such as daylight saving times and more importantly, historical changes in timezones and daylight saving times.
(Php uses the IANA/Olson timezone database.)
Background reading for newbies like me
Reading more about the following is essential:
The Database
MySql's most common data types for dates and times are:
**Type** **Format** **Range**
Date YYYY-MM-DD 1000-01-01 to 9999-12-31
Time HH:MM:SS 00:00:00 to 23:59:59
HHH:MM:SS -838:59:59 to 838:59:59
Timestamp numerical 1970-01-01 00:00:01 UTC to
2038-01-19 03:14:07 UTC
DateTime YYYY-MM-DD HH:MM:SS 1000-01-01 00:00:00 to 9999-12-31 23:59:59
PHP
**Function** **Format** **Range** date() http://www.php.net/manual/en/function.date.php timestamp range time() http://www.php.net/manual/en/function.date.php timestamp range **Class** DateTime (this class is doing all the work for us)
Note: When reading blogs, make sure about what is discussed. For example, there should be a difference between MySql date/time (referring to the individual date and time types) and datetime (a single type).
Also do not confuse MySql's date, time and datetime types (storing data) with php's date() and time() functions (getting the server's time) and php's datetime class (a class with its own functions, that we will use to do the conversions).
Also check out this amazing blog by Aaron Francis.
Locales and timezones
A user's locale will help you to convert data to the user's preferred format - such as converting yyyy-mm-dd dates to dd/mm/yy and back. These "format" conversions will not change the value of the data - only how the data is displayed.
Doing "timezone" conversions will change the value of the data - not how it is displayed.
However, the locale will not give you the user's timezone - at least not in the format that php wants it. User timezones thus need to be stored/compiled/calculated separately. Here is a list of the php supported named timezones that take care of daylight savings etc.
To make things more understandable, this wiki uses a single timezone for "timezone" conversions; and a fixed set of formats (created in the model and not retrieved from a locale) for "format" conversions. Obviously you can use separate locales and timezones for individual users.
Locales are also most important when doing language translations.
Check out the available locales in your yii\i18n\data folder.
Locale
As already stated, this wiki does not use a locale for "format" conversions, but the following is interesting to note: The user's locale is chosen by setting the language Id. This can be done in config/main.php ...
'name'=>'myWebSite', 'language' => 'en_gb', // Target language (user's language / locale) 'sourceLanguage' => 'en_us', // Source Language (app language) (default english)
Locales can also be changed in your code: Yii::app()->language='pt_br';
Timezone
Both MySql and PHP perform automatic timezone conversion - for timestamps.
MySql converts timestamps from the current time zone (by default, the server's time) to UTC for storage, and back from UTC to the current time zone for retrieval. Important: This does not occur for other types such as DateTime.
In php, the date() function either returns a passed timestamp or time(). The time() function returns the server's time after it was converted to UTC.
These timezone conversions, plus the fact that it is only performed on timestamps (not on date, time and datetime types), can make life very confusing.
So the first thing you want to do is to level the playing fields by making sure that all dates and times you get from MySql and php are in UTC (GMT +00:00). Then you don't have to worry about them any more.
Now you only have to worry about converting the data in your code from UTC to the user's timezone and back to UTC:
read data from db in UTC > convert data to user's timezone > render data
receive data from user in user's timezone > convert to UTC > write to db
Default Settings
In config/main.php:
... 'name'=>'myWebSite', /* Setting PHP timezone to UTC. This is not the database timezone, but the time zone used by php's date() and time() functions. It takes the server's time, and converts it to UTC. So even if the server's clock is set to a different timezone, this should still give you UTC. */ 'timeZone'=>'GMT', /* Setting MySql timezone to UTC. Since the database timezone is set to UTC and since timestamps are stored in UTC, no conversion of timestamps will take place in the database. Ps. If the MySql server has the time zone names installed then use 'UTC' instead of '+00:00'. */ 'components' => array( 'db'=>array( 'connectionString' => '...', ... /* SQL statements that should be executed right after the DB connection is established. */ 'initSQLs'=>array("set time_zone='+00:00';"), ...
In the model
If you missed it above: this wiki uses a single timezone for "timezone" conversions; and a fixed set of formats (created in the model and not retrieved from a locale) for "format" conversions. Obviously you want to use separate locales and timezones for individual users in your own code.
class myModel extends CActiveRecord { // User's timezone public $user_timezone = 'Africa/Johannesburg'; // yes, we have computers :) /*** PHP FUNCTION FORMATS ***/ // Between PHP and User *** RESULT *** public $php_user_short_date = 'd/m/Y'; // dd/mm/yyyy public $php_user_time = 'H:i:s'; // HH:mm:ss public $php_user_datetime = 'd/m/Y H:i:s'; // dd/mm/yyyy HH:mm:ss // Between PHP and Db (MySql) public $php_db_date = 'Y-m-d'; // yyyy-mm-dd public $php_db_time = 'H:i:s'; // HH:mm:ss public $php_db_datetime = 'Y-m-d H:i:s'; // yyyy-mm-dd HH:mm:ss protected function afterFind() { foreach($this->metadata->tableSchema->columns as $columnName => $column) { /* Test if current column is date/time/timestamp/datetime */ if (($column->dbType == 'date') || ($column->dbType == 'time') || ($column->dbType == 'timestamp')|| ($column->dbType == 'datetime')) { /* Test for null column */ if($this->$columnName === null){ $test = 0; } else{ $test = str_replace(array('/','-', '.', ':', ' '),'', $this->$columnName); } /* Continue if column is not null, else set column to false - which will prevent column being displayed in gridviews if gridview data is set like: 'value' => '($data->mycolumn) ? $data->mycolumn : "" ', */ if($test > 0) { /* Create a new php DateTime object using the date/time/timestamp/datetime retrieved from the database. Set the object's timezone to UTC (same as the server's timezone) */ $datetime_object = new DateTime($this->$columnName, new DateTimeZone('UTC') ); /* Change the DateTime object's timezone and format, based on the column's data type in the DB. Note: changing the object's timezone will automatically also change its time. */ switch ($column->dbType) { case 'date': /* Convert the object's time to the user's time */ // Do not take any action here. Date columns do // not include the time and thus cannot be // converted. /* Output the required format */ $this->$columnName = datetime_object->format( $this->php_user_short_date); break; case 'time': /* Convert the object's time to the user's time */ $datetime_object->setTimeZone(new DateTimeZone($this->user_timezone)); /* Output the required format */ $this->$columnName = $datetime_object->format($this->php_user_time); break; case 'timestamp': /* Convert the object's time to the user's time */ $datetime_object->setTimeZone(new DateTimeZone($this->user_timezone)); /* Output the required format */ $this->$columnName = $datetime_object->format( $this->php_user_datetime); break; case 'datetime': /* Convert the object's time to the user's time */ $datetime_object->setTimeZone(new DateTimeZone($this->user_timezone)); /* Output the required format */ $this->$columnName = $datetime_object->format( $this->php_user_datetime); break; } } else{ $this->$columnName = false; } } } return parent::afterFind(); } protected function beforeSave() { /* Reformat date/time/timestamp/datetime from local format and timezone to database format and UTC. */ foreach($this->metadata->tableSchema->columns as $columnName => $column) { /* Test if current column is date/time/timestamp/datetime */ if (($column->dbType == 'date') || ($column->dbType == 'time') || ($column->dbType == 'timestamp')|| ($column->dbType == 'datetime')) { /* Test for null column */ if($this->$columnName === null){ $test = 0; } else{ $test = str_replace(array('/','-', '.', ':', ' '),'', $this->$columnName); } /* Continue if column is not null. */ if($test > 0) { switch ($column->dbType) { case 'date': /* create datetime object */ $datetime_object = DateTime::createFromFormat( $this->php_user_short_date, $this->$columnName, new DateTimeZone($this->user_timezone)); /* change timezone to UTC */ // Do not take any action. Do not convert the // timezone for dates, because the time is not // included in the data saved to the db, which // means that the data cannot be converted back. /* change format to DB format */ $this->$columnName = $datetime_object->format($this->php_db_date); break; case 'time': /* create datetime object */ $datetime_object = DateTime::createFromFormat( $this->php_user_time, $this->$columnName, new DateTimeZone($this->user_timezone)); /* change timezone to UTC */ $datetime_object->setTimeZone(new DateTimeZone('UTC')); /* change format to DB format */ $this->$columnName = $datetime_object->format($this->php_db_time); break; case 'timestamp': /* create datetime object from user's format */ $datetime_object = DateTime::createFromFormat( $this->php_user_datetime, $this->$columnName, new DateTimeZone($this->user_timezone)); /* change timezone to UTC */ $datetime_object->setTimeZone(new DateTimeZone('UTC')); /* change format to DB format */ $this->$columnName = $datetime_object->format($this->php_db_datetime); break; case 'datetime': /* create datetime object */ $datetime_object = DateTime::createFromFormat( $this->php_user_datetime, $this->$columnName, new DateTimeZone($this->user_timezone)); /* change timezone to UTC */ $datetime_object->setTimeZone(new DateTimeZone('UTC')); /* change format to DB format */ $this->$columnName = $datetime_object->format($this->php_db_datetime); break; } } } } return parent::beforeSave(); } }
Important Notes:
The model's declared "PHP FUNCTION FORMATS" can be divided into two groups namely
"Between PHP and User" and "Between PHP and Db". I also added the "Result" behind each of these formats.
To ensure that DateTime::createFromFormat() will receive the data in the right format, you have to:
a) make sure that your fields/widgets in your views use formats that produce the
same "Result" as the formats in the "Between PHP and User" group;
b) make sure that your automatic timestamps that you craete in your code,
produce the same "Result" as the formats in the "Between PHP and User" group;
For example:
a) use the following formats for the CJuiDateTimePicker extension:
// JQUERY WIDGET FORMATS
public $jq_user_short_date = 'dd/mm/yy'; // Result: dd/mm/yyyy
public $jq_user_time = 'hh:mm:ss'; // Result: HH:mm:ss
b) create timestamp:
$format = $this->php_user_datetime; // Result: dd/mm/yyyy HH:mm:ss
$this->record_created_timestamp = date($format);
Remember: To test example-b, remember to set the timezone of your computer to GMT+00:00 - just like your production server - otherwise php's date() and time() functions will further convert the data. Ps. don't forget to change it back - otherwise you will be late :)
If your widget cannot produce the same "result", you could have DateTime::createFromFormat() testing for different "incoming" formats.
Tip:
The above code handles specific data types, but does not further differentiate between fields of the same data type. To improve this, some people end their column names with specific words such as ..._user_timestamp and ..._auto_timestamp. This allows you to take different action on different kind of timestamps. Just examine $columnName.
Hope this helps.