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

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

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Fixed
    • L3 - Default
    • 7.11.0, 7.11.0-alpha5
    • None
    • engine
    • None

    Description

      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:

      • External Task Log
      • Identity Link Log
      • Historic Incident
      • User Operation Log

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            Activity

              People

                miklas.boskamp Miklas Boskamp
                tassilo.weidner Tassilo Weidner
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce