Postgres SQL schema name inconsistency

deg — Wed, 24 Sep 2014 13:37:43 GMT

My dev evironment uses activiti 5.16.3 on a PostGreSQL 9.3My aciviti tables need to run in a seperate schema.I lost some time due to the fact that i gave the schema an name in uppercase. Activiti always converts the entire tablename, incuding the database schema prefix, to lowercase when trying to c

Re: Postgres SQL schema name inconsistency

deg — Thu, 25 Sep 2014 07:10:42 GMT

In addition to the above remark, in encountered what looks like a bug.
After resolving the upper , lower case problems the isTablePresent method still returns false.
As a result i still get the exception
<code>org.activiti.engine.ActivitiException: Activiti database problem: Tables missing for component(s) engine, history, identity</code>

The reason why this fails lies in the parameters passed to the <code>databaseMetaData.getTables</code> method in the code below:

<code> if ("postgres".equals(databaseType)) {
        tableName = tableName.toLowerCase();
      }

      try {
        tables = databaseMetaData.getTables(catalog, schema, tableName, JDBC_METADATA_TABLE_TYPES);
        return tables.next();
      } finally {</code>

The schema name is not passed. The tablename is the concatenation between schema and tablename. The tables are found when i pass the real tablename as a parameter in debugging mode. When i set the schema to the actual schema, instead of null as is now the case, then the tables are still found.
So to summarize:

<code>databaseMetaData.getTables(null, null, "myschema.act_ru_execution", JDBC_METADATA_TABLE_TYPES)</code> finds nothing.

<code>databaseMetaData.getTables(null, null, "act_ru_execution", JDBC_METADATA_TABLE_TYPES)</code> does find the table.

<code>databaseMetaData.getTables(null, "myschema", "act_ru_execution", JDBC_METADATA_TABLE_TYPES)</code> does find the table.

So i think i'll return to an in-memory database for a while…

topic Re: Postgres SQL schema name inconsistency in Alfresco Archive

Postgres SQL schema name inconsistency

Re: Postgres SQL schema name inconsistency