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

Hint

is related to

CAM-5990 Timestamp field inconsistencies on MySQL and MariaDB

CAM-9498 Cannot store dates / timestamps after 2038 in MariaDB/MySQL

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

CAM-10172 Introduce extra mysql queries for setting removal time async without respecting hierarchies

CAM-9506 Change column type "timestamp" for columns introduced with 7.10 for MariaDB & MySQL

CAM-9636 Remove extra queries to prevent update of fields if respective column type is timestamp for MySQL and MariaDB

(1 is related to)