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
..
mysql2_specific_schema.rb	Correctly dump native timestamp types for MySQL	2017-02-23 12:51:49 +09:00
oracle_specific_schema.rb	tests, favor public API over inspecting columns where possible.	2014-12-01 16:57:48 +01:00
postgresql_specific_schema.rb	Fix rubocop violations	2017-02-13 14:00:05 -03:00
schema.rb	Omit redundant using: :btree for schema dumping	2017-02-13 23:12:04 +09:00