New column in Actviti Table - Implication to Engine

[prakashm88]

I am using Activiti Version 5.18, with Oracle 11g.

We have a requirement to add a new column "created_date" to all the tables. We are going to use a third party tool to replicate our primary Db to a secondary DB, where the created_date column will help replicate the date to secondary DB.

My question, Will there be any implication if we add a new columns to the Activiti tables. As the tables are dropped and created newly on each Test case it was not easy for me to run all the testcases that are part of source code.

If you could help us to testing this scenario, it would be a great help. Any help is highly appreciated.

[trademak]

I don't see a direct implication of adding a column to the Activiti tables. If the column is set to NOT NULL, then there might be insert issues of course, otherwise I expect it to run just fine. You can configure the unit tests to not drop the tables as well, it's an engine configuration setting you can do in the activiti.cfg.xml file.

Best regards,

[prakashm88]

Thanks For your reply Tijs. My concern was not on dropping, but how can i create a column for the testcases.

I can have the tables already created and diable the "update schema" option. But When i have to test the whole code, its kinda reduntant.

I persume, I have to change the activiti.db2.create.*.sql directly in the activiti-engine and build from scratch.
Please let know if there are any other easier way to do the same.