In Part 1 of the training, we have learned that the Orcas operation also includes scripts which necessary data migrations can be performed. How this could be fit, we can see now.
A new addition is the ant-task “orcas_execute_one_time_scripts”. This we have informed that our scripts should lie in the directory “migrations_skripte”. This ant task we must give a clear logname (normally this is optional).
To use our project now, we still need to create the directory “migrations scripts”:
Then we can normally start the adjustment:
This does not lead initially to a substantial change because our directory “migrations_skripte” is empty.
To verify that this works we create now in the “migrations_skripte” the file “test1.sql” with the following content:
A new ant call should show somewhere in the log output “hello world”. But this only the first time, each additional call should no longer include this issue.
Orcas logs the execution of one_time_scripts. This can be viewed as required: