Hi - We''ve got a Rails application/Oracle database that we just
upgraded
from Rails 1.2 to 2.3.2 We did not have any database structural
modifications,
and thus did not need to run any migrations. However, the deployment
scripts by default include command cap deploy:migrations. Instead of
recognizing that there were no new migrations, Rails wanted to start
over and
run all migrations. The schema_info table was there, but no
schema_migrations
table. When was the schema_info table supposed to be replaced with a
schema_migrations table; shouldn''t it have happened automatically?
Should I now go in and delete the schema_info table and manually create
and
populate a schema_migrations table?
--
Posted via http://www.ruby-forum.com/.
