midPoint
Page tree

Versions Compared

Old Version 23

changes.mady.by.user Slavek Licehammer

Saved on

compared with

New Version 24

changes.mady.by.user Slavek Licehammer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following two configuration properties were reported to resolve problems with Oracle DATE attribute and PostgreSQL TIMESTAMP attribute

Code Block
<icfsdbt:nativeTimestamps>true</icfsdbt:nativeTimestamps>
<icfsdbt:allNative>true</icfsdbt:allNative>

For PostgreSQL TIMESTAMP or TIMESTAMPTZ attribute only allNative configuration property is needed

Code Block
<icfsdbt:allNative>true</icfsdbt:allNative>

In addition, the DATE, TIMESTAMP or TIMESTAMPTZ column must be provisioned as string with correct formatting, e.g.: return new Date().format("yyyy-MM-dd HH:mm:ss"), otherwise "ORA-01861: literal does not match format string" occurs (or similar exception in PostreSQL).


TIMESTAMPTZ is stored including the timezone. DatabaseTable connector doesn't work with timezone directly, but the value is automatically converted to midPoint local timezone. Therefore, you always work with local timezone in mappings and it will be automatically stored correctly in the database.