This maybe too vague a question, but I wonder if there's some wisdom out there for me to tap...
Sometimes when I get ready to commit, git says that db/schema.rb has changed. This is weird, and I think it's because I did a rake db:migrate. So my question is, what's the best practice relating to putting bits of the database (schema.rb and the databases themselves) into sourc control. And what's the best practice relating to running a rake db:migrate after a git checkout of a new branch? Anyone? - Pito -- 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.
