Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Datatype value does not display correctly in Modify schema



For any DateTime property in the application, the pxSaveDateTime is set as TIMESTAMP(6) datatype for the column associated to the property in the database. However, in the Modify schema landing page, incorrect datatype value displays, TIMESTAMP(11).

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a DateTime property.
  2. Associate the property with a column with TIMESTAMP datatype in the database.

Root Cause

This behavior is as per Pega product design.


Here’s the explanation for the reported behavior: 

According to Oracle:

Timestamp(6) indicates the precision of the digits.

For TIMESTAMP, a precision (0-9 digits) can be specified and the default is six digits. The precision is the number of digits in the fractional part of the SECOND DateTime field.

For example,

TIMESTAMP(4) can contain four numbers after the decimal separator (that is, 0.3921 seconds).

According to Pega:

Timestamp(11) or timestamp(7) indicates the bytes, that is, the size when the application is pointed to the Oracle database.

If the database changes, the bytes or the size can vary. However, data is not lost due to this difference in numbers.

Published April 7, 2019 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us