If such problematic data is inserted within the local session time zone, the session value TIME_ZONE_BEHAVIOR (changeable by ALTER SESSION) defines the course of action. Internally, the data is normalized to UTC because within certain time zones exist time shifts (for example, when switching from winter to summer time) and ambiguous periods (for example, when switching from summer to winter time). While TIMESTAMP is a simple structure consisting of a year, month, day, hour, minute, and second, data of type TIMESTAMP WITH LOCAL TIME ZONE represents a specific moment on the time axis.However, you should be aware that executing the same SQL statements in sessions with different time zones can lead to different results. Hence, users in different time zones can easily insert and display data without worrying about internal storage. In the case of TIMESTAMP WITH LOCAL TIME ZONE columns, the timestamps are internally normalized to UTC, while the input and output values are interpreted in the session time zone.Other considerations for data type TIMESTAMP WITH LOCAL TIME ZONE The range is similar to the TIMESTAMP type however, this type also considers the time zone. For more information, see ALTER SESSION and SESSIONTIMEZONE. Additionally, the data type TIMESTAMP WITH LOCAL TIME ZONE considers the session time zone. In addition to the date, TIMESTAMP contains the time. Of the various data types of the ANSI SQL standard, Exasol currently supports the DATE and TIMESTAMP types.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |