Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Timestamp - to be or not to be?
if you don't need the sub-seconds precision, you should stick to using
DATE --
it saves you quite some storage (7 bytes as opposed to 11 bytes)
and if you store timezone info it even goes up to 13 bytes ...
kind regards,
Lex.
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Mark Moynahan
Sent: donderdag 18 maart 2004 21:37
To: oracle-l_at_freelists.org
Subject: Timestamp - to be or not to be?
Hi,
Are there any technical reasons not to go forth with timestamp instead of date datatype? Are there any gotcha's by converting to timestamp?
If an application doesn't use fractions of a second is there any real need to use timestamp datatype?
Thanks,
Mark
![]() |
![]() |