I created an 001-xxx initial migration and updated it with results of a
schema::dump, removing the :force => true.
Then I ran rake migrate and (as documented) rake added a schema_info table
I've got three databases defined in database.yml using scripting I found in
Rails Recipes #17.
I defined columns only for the development database.
Happily, rake went to the development database both to dump the schema and
add the schema_info table.
Question: How did rake decide to use that database rather than test or
Is it because development is specified first in the yml file?
Is it because development is the only one with tables?
Is it because there's a setting somewhere that defaults to development but
can be modified to target other databases?
I'm running WinXP-Pro/SP2, Ruby 1.8.2-15, Rails 1.1.4, MySQL 5.0.15-nt,
SciTE 1.59, FireFox 184.108.40.206, Java JDK 1.5.0_06
Thanks in Advance,