Cast producing incorrect time after daylight savings turned on

Database
The Teradata Database channel includes discussions around advanced Teradata features such as high-performance parallel database technology, the optimizer, mixed workload management solutions, and other related technologies.
Teradata Employee

Cast producing incorrect time after daylight savings turned on

We are facing a Time Zone issue after daylight savings kicked in on 24th September.

If we cast any TIMESTAMP dated later than 24th September the result comes back with one hour subtract i.e. turned off daylight savings time.

Below is a sample query:

SELECT 
 Business_Date_Cycle_Start_Ts
 ,EXTRACT(TIMEZONE_HOUR FROM CAST(Business_Date_Cycle_Start_Ts AS TIMESTAMP(6) WITH TIME ZONE)) AS TZ_Hour
 ,CAST(Business_Date_Cycle_Start_Ts AS TIME(6)) AS Time_After_Cast
 ,EXTRACT(TIMEZONE_HOUR FROM CAST(Business_Date_Cycle_Start_Ts AS TIME(6) WITH TIME ZONE)) AS TZ_Hour_After_Cast
FROM GCFR_System_File_Extract

The results looks like below:

timstamp.png

This only happens on the casting. 

Tags (1)
1 REPLY
Teradata Employee

Re: Cast producing incorrect time after daylight savings turned on

This is working as documented.

TIME fields never include automatic daylight saving adjustment.