mournblade
Member
I have a database to which I connect to via a suite of PL/SQL scripts. The only one that is giving us trouble is the one that uses TimeStamps. I was originally using licensed version of DOA 3.4.6 to connect, but trying to pass a TDateTime resulted in the millisecond field being stored as 000.
So I try using an evaluation copy of 4.0.5 which supports timestamps. However I can't get them to work. I have changed the DeclareVariable from otDate to otTimestamp, and originally tried simply passing the TDateTime which still resulted in the milliseconds being stored as 000. So I tried passing TOracleTimestamp which wouldn't compile and had to change from SetVariable to SetComplexVariable. That "works" too but now when I view it in TOAD I get the milliseconds as 0x0 where x is a number between 1 and 9. The view changes the timestamp by "to_char(clip_start, 'hh:mi:ss:ff3')" since all I get from TOAD and SQL*Plus is "19/MAY/2003 1" and can't figure out a way of seeing the rest of the column. I've tried multiplying the milliseconds by 100, 100000, 1000000, and 1000000000 to see if that has any effect but to no avail.
Any ideas to what I am doing wrong?
So I try using an evaluation copy of 4.0.5 which supports timestamps. However I can't get them to work. I have changed the DeclareVariable from otDate to otTimestamp, and originally tried simply passing the TDateTime which still resulted in the milliseconds being stored as 000. So I tried passing TOracleTimestamp which wouldn't compile and had to change from SetVariable to SetComplexVariable. That "works" too but now when I view it in TOAD I get the milliseconds as 0x0 where x is a number between 1 and 9. The view changes the timestamp by "to_char(clip_start, 'hh:mi:ss:ff3')" since all I get from TOAD and SQL*Plus is "19/MAY/2003 1" and can't figure out a way of seeing the rest of the column. I've tried multiplying the milliseconds by 100, 100000, 1000000, and 1000000000 to see if that has any effect but to no avail.
Any ideas to what I am doing wrong?