AFAIK, migrations is simply a bunch of SQL scripts that alters your database, correct? I major difference is they're smart enough to back out the changes if anything goes wrong? I believe the reason this doesn't exist in Java is most Java applications are deployed in an environment where a DBA handles the database upgrade.
For personal deployments, I've often used the following cycle: 1. mysqldump the database 2. run the upgrade script If #2 fails, drop the database and re-import the dump. I believe there are some Java tools that've been written to accomplish Rails-like migrations, I just can't seem to find them ATM on Google. Matt On 8/10/07, Steve Jorgensen <[EMAIL PROTECTED]> wrote: > Most of the Web development I've done so far is Ruby on Rails, and I've > gotten spoiled by the great database migrations system. > > With Rails migrations, you add a migration to the project, run it, then > run the tests to see what code has to change, and then do the > application-code side of the refactoring. When you deploy into > production, you just run the db:migrate task, and it applies whatever > migrations are required to bring the database up to date, in sync with > what the code now expects. > > Is there any way to do something similar that works nicely with AppFuse > application development? > > Thanks, > > - Steve J. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
