Hi Richard What I have found when working with a sequence of migrations is that you don't really know the state of your database when something bombs. I suggest that when you come up with a different set of code for your migrations, you manually place the database in a known initial state (maybe rake db:migrate VERSION=0) and then try to run you migrations from that spot. Otherwise I have ended up with tables being created when I thought they had not or not being created when I had thought they had been.
The migrations are great when you get them figured out but if you are cramming data in as you do migrations it can get interesting. Good luck Norm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
