search for: reload_everything

TDD, SVN and migrations seem to be a natural combination for model development: create a test, add the column with a migration, write the code, and check it all in when you''re done. The trouble is that this ends up creating one migration per field. I guess it''s not horrible in and of itself, but it does have a code smell to it. Has anyone come up with a different way of doing

...Modifies trunk/vendor to use a certain rails revision (i.e. trunk or 1.1) 5. Runs trunk/vendor/rails/.../bin/rails to generate a rails directory skeleton 6. Modifies the svn:ignore for the logs and config/database.yml 7. Moves config/database.yml to config/database.yml.sample 8. Adds a script/reload_everything.sh.sample script to scripts/ that 8a. Drops the dev and test database 8b. Reloads the dev and test database 8c. Performs migration on the dev and test database 8d. Runs rake load_fixtures (to populate the dev database) 8e. Runs rake to run the tests 9. Ignores script/reload_eve...