On 11/05/2007, at 11:55 PM, Jamis Buck wrote: > Mostly because I don't think it matters 99.9% time on a first deploy, > but also because deploy:migrate already existed and it was just a one- > liner to make it happen. > > If this is problematic, though, I'd certainly entertain a patch used > db:schema:load instead of db:migrate.
cool. I'm not sure it'd work for a bunch of my apps, only because migrations assumed a schema existed beforehand; migrations weren't used to build the db from scratch. Will be sure to fix it if it ever needs fixing... -- tim --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
