Nick Tidey wrote: > Hey Fred > [...] > I understand that running the migrations end to end isn't recommended
It's pretty much a Certified Bad Idea. > but the application is what it is and because the migrations were > written prior to seed.rb being introduced, there's quite a bit of data > manipulation going on in there leaving me no choice but to re-create > the database this way. Couldn't you just do rake db:schema:load and *then* seed the DB? > Live and learn, eh. > > N. > Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
