Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-5990

Timestamp field inconsistencies on MySQL and MariaDB

    XMLWordPrintable

Details

    • Bug Report
    • Status: Closed
    • L3 - Default
    • Resolution: Duplicate
    • None
    • 7.10.0, 7.10.0-alpha6
    • engine
    • None

    Description

      By default, MySQL/MariaDB create timestamp fields such that when an UPDATE statement is performed that does not include these fields, then they are automatically updated to the current time.

      This results in several inconsistencies when we make UPDATE statements, for example:

      • task create time is updated when tasks are suspended by process definition
      • Incidents are updated due to a process definition migration

      The problem only occurs if the respective column has no further constraint or a NOT NULL constraint, which means that e. g. ACT_RU_JOB.LOCK_EXP_TIME_ is not affected as this column has a NULL constraint.

      In general, every table that uses timestamp columns may be affected, depending on the UPDATE statements we make.

      Resources:

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                thorben.lindhauer Thorben Lindhauer
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce