Code: Select all
ALTER SESSION SET TIME_ZONE='Europe/Berlin';
CREATE TABLE TEST_TIME (
ID NUMBER (28,0) NOT NULL,
TSZ TIMESTAMP(6) WITH TIME ZONE,
CONSTRAINT TEST_TIME_PK PRIMARY KEY (ID ));
INSERT INTO TEST_TIME ( ID, TSZ) VALUES ( 1, sysdate);
/
Code: Select all
select TSZ, TO_CHAR(TSZ, 'TZR') TSZ_ZONE from TEST_TIME where ID = 1
Code: Select all
28.09.2017 13:43:11,000000 +02:00 EUROPE/BERLIN
After connect, we execute
Code: Select all
ALTER SESSION SET TIME_ZONE='Europe/Berlin';
Now we query again
Code: Select all
select TSZ, TO_CHAR(TSZ, 'TZR') TSZ_ZONE from TEST_TIME where ID = 1
Code: Select all
28.09.2017 13:43:11,000000 +02:00 +02:00
Problem 2:
If we use a TIMESTAMP with local timezone column, and update to dates in January and in July, it should automatically apply a +01:00 for winter time and +02:00 for summer time.
It works fine, when you are using SQL. When you are changing the data in the grid, there is no difference between summer and winter time.
Problem 3:
In 64 bit mode, when connected to an Oracle 11g2 database, we often get an ORA-01805 "possible error in date/time operation", when trying to change data using a data grid. (Text edit, no date/time picker)