It would only ignore 001 if you had previously run 001. If you had somehow initialized the schema in production some other way (not using migrations) and then created a 001 migration to mimic that, then running it live might (depending on how that migration was defined) wipe the existing schema and start over. :(
- Jamis On 9/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > i ran deploy_with_migrations b/c i added a small db change 002, but i > still had 001 (create initial) in the deployment. should I only be > deploying the most recent migration? Very new to rails, and i guess i > assumed it would ignore 001 and move on to 002. > > On Sep 7, 4:03 pm, "Jamis Buck" <[EMAIL PROTECTED]> wrote: > > The only way cap deploy_with_migrations would wipe your data is if you > > have a pending migration that wipes your data. All > > deploy_with_migrations does is (after deploying) call "rake > > RAILS_ENV=production db:migrate", so you'll want to check the > > migrations you have defined to see what's there. > > > > - Jamis > > > > On 9/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > > > > > I just did a cap deploy_with_migrations while playing around with > > > capistrano. Now, all of the data in my database is wiped out. Did I > > > really just destroy all of that? > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
