Archives of the TeradataForum
Message Posted: Thu, 12 Jun 2008 @ 11:26:09 GMT
> 2008-06-11 11:03:10.490000+00:00
This is the expected behavior:
"The seconds precision of the result of CURRENT_TIMESTAMP is limited to hundredths of a second. CURRENT_TIMESTAMP returns zeros for any digits to the right of the two most significant digits in the fractional portion of second"
BTEQ or ODBC? It does not matter in this case. Here's what BTEQ provides:
BTEQ -- Enter your DBC/SQL request or BTEQ command: sel current_timestamp; sel current_timestamp; *** Query completed. One row found. One column returned. *** Total elapsed time was 1 second. Current TimeStamp(6) -------------------------------- 2008-06-12 12:07:22.580000+00:00
The quote is from a manual which is a couple of years old. There is always a possibility something changed in the recent releases. Perhaps somebody will be able to produce more accurate current timestamps?
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|