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

Seperate Schema for Camunda tables requires TablePrefix which results in error on table checks

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Duplicate
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • engine

      Situation:

      • Schema for Camunda tables != User Schema of Username/Password of Datasource
      • Then you have to configure the Schema Name
      • Only possibility to do this currently is to set TablePrefix: "SCHEMA."
      • This works well for MyBatis Statements (SELECT ${prefix}ACT_...).
      • It does NOT work for checking the existence of the tables - because there the Schema name AND TablePrefix is taken into account with leads to table name "${schema}.${prefix}TableName".

      Workaround:

      • Set property "databaseSchemaUpdate " to an non existing value (database checking is skipped completely):
        ProcessEngineConfiguration.databaseSchemaUpdate = "NOOP"

      In the shared engine configuration this looks like:

      <property name="databaseSchemaUpdate">NOOP</property>
      <property name="databaseTablePrefix">SCHEMA_NAME.</property>

      See http://docs.camunda.org/7.3/api-references/deployment-descriptors/#tags-process-engine-configuration-configuration-properties

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              ruecker Bernd Ruecker
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: