Loading...

XML

Word

Printable

Steps to reproduce
Setup the Engine with a MariaDB or MySQL database

If an update statement is executed against a table that has columns of type TIMESTAMP without any constraint or with constraint NOT NULL, ...

Observed behavior
...the value of these fields are automatically updated with the current timestamp

Expected behavior
... the original timestamp value of these fields are preserved

Root cause

if a table is created without any constraint on column of type TIMESTAMP or with constraint NOT NULL, the implicit default value is timestamp(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3) ON UPDATE CURRENT_TIMESTAMP(3) and the field is updated with the current timestamp
if a table is created with NULL constraint on column of type TIMESTAMP, the respective field is not updated with current timestamp as the implicit default value is NULL DEFAULT NULL

AT
Extra queries are introduced for:

depends on

CAM-10133 Using Java API, I can set a removal time for processes asynchronously without respecting hiearchies

is related to

CAM-9505 On MariaDB and MySQL an update operation leads to an update of date fields if column type is timestamp

CAM-10664 Introduce extra update statement to prevent updating the timestamp with mysql

CAM-10130 I can set a removal time for processes asynchronously

CAM-10132 Using Java API, I can set removal time for batches asynchronously