David A. Black wrote:

> It doesn't appeal to me not to use the model generator. For one thing,
> I assume that it would mean having to run sequential migrations, where
> you wrote a test or spec that tested for the presence of, say, a
> first_name attribute on the user; then add that column to the
> database; then test for last_name; then add that column; and so forth.
> I don't mean to sound like I'm parodying what Steve is describing. I
> assume that this, or something like it, is what you'd end up doing.

Parenthetically, you are "allowed" to edit a pre-existing migration file, if you 
can keep track of which VERSION your production database has.

Within that loop, yes, write a test that fails because MyModel has no has_many 
NotherModel, then pass it by adding a column :nother_model_id to the migration.

-- 
   Phlip