You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MySQL converts TIMESTAMP values from the current time zone to UTC for storage, and back from UTC to the current time zone for retrieval. (This does not occur for other types such as DATETIME.)
This sounds like this type has point-in-time semantics, so we should map it to a point-in-time Trino type.
Until we have #2273, this should be timestamp with time zone.
The text was updated successfully, but these errors were encountered:
When working on that it may be worth exercising MySQL DATETIME and MySQL TIMESTAMP column mappings (the TestMySqlTypeMapping class) against MySQL instances with different server time zones.
This was solved for MySQL, but no change applied in MariaDB and SingleStore, both being forks of MySQL (AFAIK). @hashhar@adamjshook Do we need fixes for these connectors as well?
Currently MySQL
TIMESTAMP
is mapped to Trinotimestamp
.Per https://dev.mysql.com/doc/refman/8.0/en/datetime.html
This sounds like this type has point-in-time semantics, so we should map it to a point-in-time Trino type.
Until we have #2273, this should be
timestamp with time zone
.The text was updated successfully, but these errors were encountered: