From: Matt Harrison <iwasinnamuknow@...>
Date: 2009-01-12T03:05:56+09:00
Subject: Re: reccommended work flow for unit tests and databases in ruby

Phlip wrote:
> Investigate (and use!) the ActiveRecord system exemplified in Rails 
> fixtures and migrations. When your program starts, only only _only_ put 
> in the database the very few fields you are actually using. Rails's 
> "script/generate model" will write a migration which adds that table to 
> the db. Write tests for the model's behavior, and these will require 
> fields in the table. Edit the model's migration file to add them. Repeat 

This sounds great, but I've read in several places (sorry can't find 
references) that you should create a new migration to make changes to an 
existing table.

I've tried before to modify an existing migration but unless I totally 
wipe the DB, it doesn't take notice, as the schema version isn't 
incremented.

Is this expected behavior or am I doing something wrong?

--
Matt