I don't want to add schema.rb to .gitignore, because I want to be able to load a new database schema from that file. However, keeping it checked in is causing all sorts of spurious conflicts that are easily resolved by a fresh db:migrate:reset. Basically I want a way to: Keep schema.rb in the repository for deploy-time database setup...
Im trying to add an extra field to one of my tables. Ive added the field in the migration file (under db\migrate) then ran 'rake db:migrate' which ran without troubles and my text editor even told me my schema.db file has been updated and needs to refresh. The schema file does not contain my new field and any attempts to reference the ...
It's possible to replace db/migrate/* with the contents of db/schema.rb, so that you only have one migration step. Do any of you ever do this? Why? ...