AnsweredAssumed Answered

Activiti SQL for upgrading from 5.2 to 5.3...

Question asked by wolpert on Mar 3, 2011
Latest reply on Mar 4, 2011 by frederikheremans1
Folks-

  We use liquibase to manage our database, so I need to create a SQL script for updating from 5.2 to 5.3. For this, I'm planning on just doing the following:

1) Copy the SQL from activiti.postgres.upgradestep.52.to.53.history.sql
2) following SQL updates:
update act_ge_property set rev_ = 2, value_ = '5.3' where name_ = 'schema.version';
update act_ge_property set rev_ = 2, value_ = 'create(5.1) upgrade(5.1->5.3)' where name_ = 'schema.history';
insert into act_ge_property (name_, value_, rev_) values ('historyLevel','2',1);

(Note that the 'schema.history' I'm setting was how it was done in my developer instance.)

Is this correct? Is there a way to execute the activiti upgrade process, but have it printout the pending SQL and not execute it? Is there a better way? (I suppose I could clone my current db to a local instance, turn logging on my db to full, run the upgrade in a local instance, and manually copy the resulting SQL to a liquibase script…)

Outcomes