Archives of the TeradataForum
Message Posted: Mon, 04 Nov 2013 @ 10:44:54 GMT
| Subj: || || Re: CAST(CURRENT_TIME AS TIME) reporting wrong time in TD 14.0 |
| From: || || Anomy Anom |
<-- Anonymously Posted: Monday, October 21, 2013 05:28 -->
Fred Pluebell wrote:
| ||More likely, you just had a zero time zone offset on prior release and nonzero in TD14.0.|| |
| ||In case 1, CURRENT_TIME (which is a TIME WITH TIME ZONE) is first converted to UTC (GMT) using its included time zone offset (which
currently reflects 1 hour daylight saving adjustment), then the session / user / system time zone (without any daylight saving adjustment) is
applied to give the result.|| |
| ||Perhaps not the result you expect, but working as designed.|| |
| ||In case 2, all times are effectively converted to TIMESTAMP using CURRENT_DATE, then normalized to UTC/GMT using the included TIME ZONE for
CURRENT_TIME and the session / user / system time zone offset for the CASTs (again without any daylight saving adjustment), and the timestamps
Thank you Fred.
But after TD 14.0 upgrade, we are storing DateTime values in systemLocalTime.
"57. TimeDateWZControl = 3? (Enabled with LOCAL)"
So, am not sure if does the Built-in functions like CURRENT_TIME ( CASE 1 ) and TIME
Comparisons ( CASE 2 ) still functions the same way with the above setting.