WebSockets: Wrong values for TIMESTAMP WITH LOCAL TIME ZONE columns
Details
| Detail name | Value |
|---|---|
| Changelog Number | 9962 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | EXASOL 6.0.0, Exasol 6.1.0, Exasol 6.2.0, Exasol 7.0.alpha1 |
| Fix Versions | Exasol 7.0.0, Exasol 6.1.9, Exasol 7.0.beta1, Exasol 6.2.6 |
| Resolution Date | 2020-04-17 |
Problem
When using WebSockets with TIMESTAMP WITH LOCAL TIME ZONE columns, the values may be incorrectly converted to the wrong time zone.
The values may be incorrect in the following scenarios.
- Using WebSockets to retrieve data from Exasol.
- Using WebSockets to insert data into Exasol using a prepared statement.
Example
> ALTER SESSION SET TIME_ZONE='EUROPE/BERLIN'
> CREATE TABLE T1(C1 TIMESTAMP WITH LOCAL TIME ZONE)
> INSERT INTO T1 VALUES ('2020-04-14 12:00:00')
> SELECT * FROM T1
-- "2020-04-14 14:00:00.000000" (correct: "2020-04-14 12:00:00.000000")
> ALTER SESSION SET TIME_ZONE='EUROPE/MOSCOW'
> SELECT * FROM T1
-- "2020-04-14 16:00:00.000000" (correct: "2020-04-14 13:00:00.000000")
