Use timezone from connection options

[noamw]

'SELECT FROM_UNIXTIME(631152000)' returns the timestamp in local tz instead of UTC (e.g. for PST, equivalent of 1990-01-31T22:00:00.000Z instead of expected 1990-01-01T00:00:00.000Z)

Simliar issue in mysql-native has been proposed a fix in sidorares/nodejs-mysql-native#78

[sidorares]

Can you give links to other APIs with similar functionality (e.i why UTC and not local tz?) Command line client resut:

mysql> SELECT FROM_UNIXTIME(631152000);
+--------------------------+
| FROM_UNIXTIME(631152000) |
+--------------------------+
| 1990-01-01 11:00:00      |
+--------------------------+
1 row in set (0.01 sec) 

[noamw]

The proposed fix in sidorares/nodejs-mysql-native#78 indeed converts to UTC as that is the only invariant that can allow for simple coherent API. The other way would be to support time zone conversions, assuming that indeed all users of the library always make use of them (like done in node-mysql).

However, the problem reported here is not specific to that approach - if you use the tz approach, it makes perfect sense you will receive the result in the client timezone as in your example, but please note that in my example, the local time is returned, but it is as if that value is in UTC time zone (notice the Z) !!!!

[sidorares]

With FROM_UNIXTIME example timezone does not matter - you get js Date object pointing to that 631152000 time.
With DATETIME with no tz info I'll probably add 'use tz from config if present'.

> a = _rows[0]['FROM_UNIXTIME(631152000)']
Mon Jan 01 1990 11:00:00 GMT+1100 (EST)
> a.toGMTString()
'Mon, 01 Jan 1990 00:00:00 GMT'
> a.toISOString()
'1990-01-01T00:00:00.000Z'