All Forums General
reena2485 3 posts Joined 09/14
16 Oct 2014
compution logic of this td_week_begin function when first argument is timestamp and last third argument is time literal

I am exploring business calendar functions in teradata. There are some of the business calendar functions like td_week_begin, td_week_end, which takes timestamp with time zone value in first argument and time literal value in third argument, Second argument is the calendar type like iso, teradata.
Example: 
SELECT TD_WEEK_BEGIN(TIMESTAMP'2014-10-13 15:25:02+10:00','ISO',TIME'09:12:05');
I wanted to know the compution logic of this td_week_begin function when first argument is timestamp and last third argument is time literal. When I do not pass the third optional argument, time literal, I know how this function works, but when for the same value of first argument, If I pass time literal value, the result get change. Somehow this time literal value impacts the value of first argument.
I wanted to know, how this time literal affects timestamp with time zone value.
Please help me in understanding this specific scenario, 

Tags:
Raja_KT 1246 posts Joined 07/09
17 Oct 2014

This doc is a good read:
http://www.info.teradata.com/HTMLPubs/DB_TTU_14_10/index.html#page/SQL_Reference/B035_1145_112A/Business_Calendars.080.001.html#ww1270902

Raja K Thaw
My wiki: http://en.wikipedia.org/wiki/User:Kt_raj1
Street Children suffer not by their fault. We can help them if we want.

You must sign in to leave a comment.