Ryuta Kamizono 505526335b Correctly dump native timestamp types for MySQL ... The native timestamp type in MySQL is different from datetime type. Internal representation of the timestamp type is UNIX time, This means that timestamp columns are affected by time zone. ``` > SET time_zone = '+00:00'; Query OK, 0 rows affected (0.00 sec) > INSERT INTO time_with_zone(ts,dt) VALUES (NOW(),NOW()); Query OK, 1 row affected (0.02 sec) > SELECT * FROM time_with_zone; +---------------------+---------------------+ | ts | dt | +---------------------+---------------------+ | 2016-02-07 22:11:44 | 2016-02-07 22:11:44 | +---------------------+---------------------+ 1 row in set (0.00 sec) > SET time_zone = '-08:00'; Query OK, 0 rows affected (0.00 sec) > SELECT * FROM time_with_zone; +---------------------+---------------------+ | ts | dt | +---------------------+---------------------+ | 2016-02-07 14:11:44 | 2016-02-07 22:11:44 | +---------------------+---------------------+ 1 row in set (0.00 sec) ```		2017-02-23 12:51:49 +09:00
..
active_record/connection_adapters	Add more rubocop rules about whitespaces	2016-10-29 01:17:49 -02:00
assets	Use YAML to serialize schema cache	2016-11-27 22:09:58 -05:00
cases	Correctly dump native timestamp types for MySQL	2017-02-23 12:51:49 +09:00
fixtures	Correct spelling	2017-02-05 19:00:18 -06:00
migrations	modernizes hash syntax in activerecord	2016-08-06 19:37:57 +02:00
models	Fix inspection behavior when the :id column is not primary key	2017-02-09 01:57:50 +09:00
schema	Correctly dump native timestamp types for MySQL	2017-02-23 12:51:49 +09:00
support	fix #create_fixtures when equal table names in different databases	2016-12-21 11:09:29 +01:00
.gitignore	…
config.example.yml	Fix tests for prepared_statements: false and queries hitting `#select_all`	2016-11-19 21:52:52 +05:30
config.rb	…