Having the ability to do DB migrations on startup isn't bad. Frankly it's nice when you don't care, like dev/test. You should just be able to additionally do it as a step before. I know this is technically possible as the mvn deploydb does this somehow.
The larger problem is that 1) it is a custom framework 2) has SQL in compiled code. Most DBAs I've known really don't care for fancy migration frameworks. But they do serve a good purpose. So as long as it's a well known, well documented, and transparent framework, they tend to accept it. Transparent meaning they have some way to know what SQL will be executed before they kick off the program. Again, I'll probably look into this more in the future. Right now just gathering info. Darren On Aug 28, 2013, at 7:20 AM, Alex Huang <alex.hu...@citrix.com> wrote: > There's DatabaseCreator.java which upgrades the database. That's how we're > creating the database. We can pretty much replace the checker with something > that only checks the version rather than upgrades the database from the xml > file. > > --Alex > >> -----Original Message----- >> From: Darren Shepherd [mailto:darren.s.sheph...@gmail.com] >> Sent: Tuesday, August 27, 2013 4:48 PM >> To: dev@cloudstack.apache.org >> Subject: database upgrades >> >> It seems like on startup of the management server >> DatabaseUpgradeChecker runs and upgrades the database performing DDL >> and DML. Is there a way to upgrade the database that doesn't include >> starting the management server? >> >> Darren
