Matt, Thanks for a great summary; very helpful, and thanks to the rest of the list for always providing insightful comments and solutions to problems. Great!!
- Pito Matt wrote: > Pito, > > I'm going to leave the entire db version control question for someone > else, but to answer your question about the schema.rb, if you run a > migration, it will change the structure of the database, which is what > schema.rb keeps track of. Rails will rewrite that file every for every > migration ran to reflect the current structure of the db ( structure > as in tables, column names, indexes, etc... Not data the records > stored in the db ). This file should be checked into git, and like any > file that changes under version control, git will let you know about > the changes and track them. > > As your app grows, your migration files will be more prone to hving > problems and shouldn't be used to create / setup the database. The > schema file is much better at recreating the db structure when > starting fresh ( like if you have to scale up your app and create a > new db on another server ). There are rake tasks for this, such as > rake db:reset ( caution, that one will wipe out all data in db), so > read up on them and they can save you many headaches as you have to > move your databases around. > > -Matt -- 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.
