Pito Salas wrote: > 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.
Yes, that would probably be why. Why do you think this is "weird"? It's normal behavior -- schema.rb contains what Rails thinks your database schema is. > > So my question is, what's the best practice relating to putting bits of > the database (schema.rb and the databases themselves) schema.rb is not a "bit of the database". > into sourc > control. And what's the best practice relating to running a rake > db:migrate after a git checkout of a new branch? To summarize my earlier posts: schema.rb definitely goes into version control. I don't bother putting SQLite databases themselves in the repository, though (not that I use SQLite much). > > Anyone? > > - Pito Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- 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.
