TO_CHAR(msg_date, 'HH24:MI:SS.FF ') 2005-01-20 - By Looney, Jason
The difference is between SYSDATE and SYSTIMESTAMP. SYSTIMESTAMP is a
TIMESTAMP and the extended format is available. SYSDATE does not contain
milliseconds or timezone information. If you change the column def of
saud_log to TIMESTAMP, then your select from saud_log will work as well.
Jason.
-- --Original Message-- --
From: Leonard, George [mailto:GLeonard@(protected)]
Sent: Wednesday, January 19, 2005 10:38 PM
To: oracle-l@(protected)
Subject: TO_CHAR(msg_date, 'HH24:MI:SS.FF')
Hi all,
Example of insert string
Insert into saud_log (sysdate(),'some text');
Commit;
I now want to retrieve the text in date/time order.
Since multiple insert can occur from the same package in a second I want
to fine tune it to milliseconds.
But the below query is complaining about ora-01821 (See ora-01821.ora-code.com) date format not
recognised
select TO_CHAR(msg_date, 'HH24:MI:SS.FF4'), msg_desc from saud_log order
by msg_date desc;
but I can run=20
SELECT TO_CHAR(SYSTIMESTAMP, 'HH24:MI:SS.FF4') from dual;
ideas
George
=20__ ____ ____ ____ ____ ____ ____ ____ ____ _____
George Leonard
Oracle Database Administrator
New Dawn Technologies @ Wesbank
E-mail:gleonard@(protected)
=20
You Have The Obligation to Inform One Honestly of the risk, And As a
Person
You Are Committed to Educate Yourself to the Total Risk In Any Activity!
Once Informed & Totally Aware of the Risk,
Every Fool Has the Right to Kill or Injure Themselves as They See Fit!
=20
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ _____=
__ ____ ____ ____ ____ ___
The views expressed in this email are, unless otherwise stated, those of =
the author and not those
of the FirstRand Banking Group an Authorised Financial Service Provider o=
r its management.
The information in this e-mail is confidential and is intended solely for=
=20the addressee.
Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, any disclosure, copying, distribut=
ion or any action taken or=20
omitted in reliance on this, is prohibited and may be unlawful.
Whilst all reasonable steps are taken to ensure the accuracy and integrit=
y of information and data=20
transmitted electronically and to preserve the confidentiality thereof, n=
o liability or=20
responsibility whatsoever is accepted if information or data is, for what=
ever reason, corrupted=20
or does not reach its intended destination.
=20 __ ____ ____ ____ ____ ____ ____
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
|
|
