Support Article
DB column of datatype Timestamp stores data without milliseconds
SA-44811
Summary
Initiating a Connect SQL rule to insert a DateTime property to a TIMESTAMP column in an Oracle database, stores milliseconds as 000000 instead of the actual value.
For example,
Inserted property value: 20170915T125422.195 GMT
Value actually stored in database column: 15-SEP-2017 08:54:22.000000
Error Messages
Not Applicable
Steps to Reproduce
- Create an external database table in Oracle database where one of the columns is a TIMESTAMP.
- Create an Connect SQL rule to insert to the table.
- Insert a Timestamp value with milliseconds in it when invoking the RDB-SAVE.
Root Cause
This issue was determined to be a product enhancement request.
Resolution
Perform the following local-change:
- Map a class to the database table using the external database class mapping wizard.
- Use Obj-Save instead of RDB-Save. Obj-Save stores the millisecond precision.
Published February 18, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.