Timestamp in Hyperion (Brio) 9.3.1 and Teradata V2R6.1

Third Party Software
gb
Fan

Timestamp in Hyperion (Brio) 9.3.1 and Teradata V2R6.1

Hi,

Would anyone know why the difference of two timestamp(6) columns in interval day(4) to second(6) is coming out all nulls in Hyperion 9.3.1? A calculated field with formula "(col2 - col1) interval day(4) to second(6)" is always NULL even though the two columns have different timestamp values.

Just to give you an idea, below is the equivalent in SQL Assistant that works:

create volatile table mytable ( col1 timestamp(6) , col2 timestamp(6) ) primary index (col1) on commit preserve rows;

delete from mytable;
insert into mytable
values (
current_timestamp (timestamp(6)) --- current time
, timestamp '2010-04-30 00:00:00.000000' --- time in the future
);

select
(col2 - col1) day(4) to second(6) as dy2sec
from mytable ;

Is this incompatibility between Hyperion and Teradata? Is there a work-around?

Thank you for any help.

Cheers,

GB

1 REPLY
Teradata Employee

Re: Timestamp in Hyperion (Brio) 9.3.1 and Teradata V2R6.1

Hi GB,

I don't know if this is a bug or not. I have a workaround suggestion, though. In teradata, create a view that has your interval column. Then use Hyperion to pull from the view column.

Steve