Run Changes

If you choose not to run Firefly automatically, you can start it via ant. Use the firefly-update target to start the ugrade. To see the upcoming changes to your database use the ant firefly-simulate target.

During development to you may want to start the changes without using ant or restarting the server. For this, you can use the hAC groovy console.

   ctx.getBean('fireflyService').migrate()
   println 'done'

   println ctx.getBean('fireflyService').simulate()

Running Groovy-Changes

If you use the println command in a groovy change, the result will be added to you log file automatically while the script is running. This is usefull if you have some changes that take a while and want to follow the progress.

Running SQL-Changes

Every change is commited automatically. So you should not use a commit within a change.

Also keep in mind, that most DB systems (like oracle) perform a auto commit after a DDL (Data Definition Language) command. So you chould create seperate changes for those type of commands. This way, Firefly can resume the update even if one command fails.