On Feb 11, 9:42 pm, Adam <adam.steg...@gmail.com> wrote: > Sure enough, I see that exact information in the Migration > documentation.http://api.rubyonrails.org/classes/ActiveRecord/Migration.html > It works great now. Thank you. >
You should also be careful about using model classes in migrations - because your source is updated in one go but migrations run one by one it's easy enough to run into trouble. For example if your model has a validation on a column that is added by migration two and migration one tries to create some objects of that class then it will fail because of the validation on the not yet existent column Fred -- 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 rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
