Marnen Laibow-Koser wrote in post #961663: >> >> I used skip-migration because the table already exists in mysql. >> When I move from learning mode to development mode, I will need to write >> code against existing databases, so I can't maintain the database source >> code in ruby. > > That's not quite true. You need to learn about rake db:schema:dump.
Let me rephrase .. I don't want to depend on ruby for schema definition, even if it can do it. Anyway, I did the migrate separately, like this: rake db:migrate It brought all the table definitions over from my mysql database. > > Anyway, you should be using migrations wherever possible, especially as > you learn. -- 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 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.
