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

Check for table presence fails when a schema table prefix is used

    Details

    • Type: Bug Report
    • Status: Closed
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: 7.2.2
    • Fix Version/s: 7.3.0, 7.2.5, 7.1.10, 7.3.0-alpha4
    • Component/s: None
    • Labels:
    • Title Keywords:
      spring tablePrefixIsSchema processEngineConfiguration

      Description

      See https://jira.codehaus.org/browse/ACT-1940

      If on all supported databases, a schema prefix is identified by a dot, a nicer fix would be to look for a dot in the databaseTablePrefix property.

        Issue Links

          Activity

          Hide
          thorben.lindhauer Thorben Lindhauer added a comment -

          Hi,

          Where did you find the property "tablePrefixIsSchema" and for what is it used/should it be used?

          Cheers,
          Thorben

          Show
          thorben.lindhauer Thorben Lindhauer added a comment - Hi, Where did you find the property "tablePrefixIsSchema" and for what is it used/should it be used? Cheers, Thorben
          Show
          Dimitri Dimitri Lubenski added a comment - Please check https://jira.codehaus.org/browse/ACT-1940 It is available in the: http://activiti.org/javadocs/org/activiti/engine/ProcessEngineConfiguration.html Cheers, Dimitri
          Hide
          thorben.lindhauer Thorben Lindhauer added a comment -

          Ok, I updated the bug description accordingly.

          Thanks for reporting.

          Show
          thorben.lindhauer Thorben Lindhauer added a comment - Ok, I updated the bug description accordingly. Thanks for reporting.
          Hide
          Dimitri Dimitri Lubenski added a comment - - edited

          Thanks a lot.

          Please keep in mind, that currently the workaround <property name="databaseSchemaUpdate" value="none" /> has to be used in order to assure, that the engine can start. This is a workaround and is not documented.

          The situation occurs in cases where oracle is used, and you access the DB from the web application using e.g. APP_USER while the tables are created in the ADMIN_USER. This is usually done to implement security reducing the permissions for the APP_USER to the minimum.

          Having
          <property name="databaseSchema" value="ADMIN_USER" />
          <property name="databaseTablePrefix" value="ADMIN_USER." />
          <property name="databaseSchemaUpdate" value="false" />

          does not solve the issue, because the version check is performed during the engine startup (spring initialization) and the table with the version cannot be found.

          This post can also be helpful http://forums.activiti.org/content/tables-missing-components-engine-history-identity

          Show
          Dimitri Dimitri Lubenski added a comment - - edited Thanks a lot. Please keep in mind, that currently the workaround <property name="databaseSchemaUpdate" value="none" /> has to be used in order to assure, that the engine can start. This is a workaround and is not documented. The situation occurs in cases where oracle is used, and you access the DB from the web application using e.g. APP_USER while the tables are created in the ADMIN_USER. This is usually done to implement security reducing the permissions for the APP_USER to the minimum. Having <property name="databaseSchema" value="ADMIN_USER" /> <property name="databaseTablePrefix" value="ADMIN_USER." /> <property name="databaseSchemaUpdate" value="false" /> does not solve the issue, because the version check is performed during the engine startup (spring initialization) and the table with the version cannot be found. This post can also be helpful http://forums.activiti.org/content/tables-missing-components-engine-history-identity

            People

            • Assignee:
              thorben.lindhauer Thorben Lindhauer
              Reporter:
              Dimitri Dimitri Lubenski
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development