cancel
Showing results for 
Search instead for 
Did you mean: 

Having old and new version of activiti looking to same db

xseagullx
Champ in-the-making
Champ in-the-making
Hello.

I'm updating DB, and trying to go from activiti 5.14 to 5.16.4, but It seems my processes are broken now.
I need a temporary solution, to be able to continue work with old engine, till i'm updating code and processes. I can't create another database now, and I have already updated a schema to 5.16.4

Can I ask activiti to ignore version incompatibility, and run older engine on a new database?
Both options(true/false) for databaseSchemaUpdate will end up with an exception(different, but still).

Thanks,
Pavel
2 REPLIES 2

xseagullx
Champ in-the-making
Champ in-the-making
As far as I understood, there is no way avoid that check, but it may be workarounded manually changing version in DB. It probably will not break anything, as schema changing is backward-compatible.

So, I'll stick with this solution, even if it's not too safe, and need some manual work by hacking db value before starting specific engine.

trademak
Star Contributor
Star Contributor
Hi Pavel,

Like we discussed yesterday it should work fine, but no guarantees.

Best regards,