Binary protocol support for MySQL 8.0.19 TIMESTAMP/DATETIME values with timezone details

[vlasky]

Support for Datetime literal values with a specified time zone displacement was introduced in MySQL 8.0.19:

https://dev.mysql.com/worklog/task/?id=10828

Datetime literal values with a specified time zone displacement shall be accepted. Time zone displacement syntax uses the format {+-}HH:MM and is appended to a regular datetime literal with no intervening whitespace. The literal is generally interpreted as a local time value that can be converted to UTC by subtracting the time zone displacement from the date/time value. The valid range is -14:00 to +14:00, where -00:00 is not allowed, compliant with the SQL standard. Examples:

2015-10-01 11:59:59-02:00 is 2015-10-01 13:59:59 UTC.
2015-10-01 11:59:59.999999+05:30 is 2015-10-01 06:29:59.999999 UTC.

The client/server binary protocol has been extended to allow the timezone details to be passed as part of the datetime/timestamp value. I presume that node-mysql2 will now need to incorporate this:

https://dev.mysql.com/worklog/task/?id=10828#tabs-10828-5

[sidorares]

thanks for pointing, super keen to implement this, TZs were always a pain to manage