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

XML

Word

Printable

Details

Type: Task
Status: Closed
Priority: L3 - Default
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 7.11.0, 7.11.0-alpha2
Component/s: None
Labels:
None

Description

Problem

~~CAM-9505~~ introduces a fix that prevents fields of column type timestamp from being updated on UPDATE statement
The fix introduces extra queries for MySQL-like databases
On migrating the column type from timestamp to datetime these extra queries are not needed anymore

AT
Extra queries are removed for migrated columns

Hint
The following extra queries were introduced:

updateIncident_mysql
updateTaskSuspensionStateByParameters_mysql
updateJobLogByBatchId_mysql
updateJobLogByRootProcessInstanceId_mysql
updateUserOperationLogByRootProcessInstanceId_mysql
updateExternalTaskLogByRootProcessInstanceId_mysql
updateHistoricIncidentsByBatchId_mysql
updateHistoricIncidentsByRootProcessInstanceId_mysql
updateIdentityLinkLogByRootProcessInstanceId_mysql

mgm-controller-panel

This is the controller panel for Smart Panels app

Attachments

Issue Links

depends on

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

Closed

is related to

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

Closed

Activity

People

Assignee:: Unassigned

Reporter:: Tassilo Weidner

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 11/Jan/19 4:16 PM

Updated:: 01/Mar/19 12:51 PM

Resolved:: 22/Feb/19 9:28 AM

Salesforce