Hi Bob, yes, I'm using 'm' to apply the migrations.
If I don't, I get a message about having "pending migrations" and I need to run "bundle exec rake db:migrate" to solve that and allow the next 'hobo g migration' to work. Having run "hobo g migration" and accepted the migration with 'm', if I run 'hobo g migration' again, then hobo wants to add three fields with default values, again. If I accept that with an 'm', and re-run, exactly the same thing will happen. I got bored when I reached the 7th repetition - more than enough proof that it is repeatable, I think ;) . It happens consistently and persistently for me (using 1.9.2p290, rails 3.0.11, hobo 1.3 - I haven't tried any other combinations). Thanks, JeremyC On Jan 1, 3:33 pm, Bob Sleys <[email protected]> wrote: > When you run the hobo g migration do you choose the option to 'm' to run > the migration after creating it? I believe Hobo just compares the actual > database to the models looking for changes so if you only create the > migratino files but don't migrate the database it won't "see" the previous > migration and do it again. You need to migrate the database between each > hobo g migration iteration and not just create the migration files > themselves. > > Bob -- You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en.
