cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with schemas in PostgreSQL

blopes
Champ in-the-making
Champ in-the-making
Hi everybody, I'm trying to use Activiti 5.12.1 in Grails 2.2.2 and generate its tables in a different schema in PostgreSQL 9.1. Using the default schema (public) it works very nice, but trying to use with another schema (activiti, for instance), I see the same error as in http://jira.codehaus.org/browse/ACT-1610.  I have created the tables, and Activiti is able to find then, but this error happens.
Is there a workaround to this situation?

My activiti.cfg.xml is as follow:

<blockcode>
   <bean id="processEngineConfiguration" class="org.activiti.engine.impl.cfg.StandaloneProcessEngineConfiguration">
                <property name="processEngineName" value="activiti-engine" />
      <property name="jdbcUrl" value="jdbcSmiley Tongueostgresql://localhost/localbd" />
      <property name="jdbcDriver" value="org.postgresql.Driver" />
      <property name="jdbcUsername" value="postgres" />
      <property name="jdbcPassword" value="postgres" />
                <property name="databaseSchema" value="activiti" />
                <property name="databaseTablePrefix" value="activiti." />
      <property name="databaseSchemaUpdate" value="false" />
      <property name="jobExecutorActivate" value="false" />
      <property name="mailServerHost" value="mail.my-corp.com" />
      <property name="mailServerPort" value="5025" />
   </bean>
</blockcode>

Thanks in advance. If you need more clarifications, let me know.
3 REPLIES 3

trademak
Star Contributor
Star Contributor
Hi Bruno,

Yes that's a known issue. We plan to fix that in the next release (5.13.1). In the meantime what you can do is create the schema with our DDL files and set the databaseSchemaUpdate value to "none". And then  only set the databaseTablePrefix value to your schema name.

Best regards,

balunadig
Champ in-the-making
Champ in-the-making
Hi Tijs:

I am using 5.14/515 activiti wiith H2. I am trying to get a named schema work with it.

property name="databaseSchema" value="ACTIVITIDS"
property name="databaseTablePrefix" value="ACTIVITIDS."
property name="databaseSchemaUpdate" value="none"

Do I still need to do create schema activitiDS and the qualifier (activityDS.) to the ddl?

trademak
Star Contributor
Star Contributor
Hi,

Yes, we didn't do any changes to this logic yet.

Best regards,