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).
Steps to Reproduce
- Create a DateTime property.
- Associate the property with a column with TIMESTAMP datatype in the database.
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.
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.
0% found this useful