We upgraded our app from Rails 1.2 to 2.3. There were no outstanding database migrations, i.e. the database was up-to-date during the upgrade/deployment process. The schema_migrations table was created, but it was not populated and the schema_info table was not removed. Can anyone explain why the new schema_migrations table would be created but the data from the schema_info table not used to insert values into it? Everything I've read about the upgrade process says the schema_info table would automatically be replaced with the schema_migrations table; does this not include actually populating the new table?? -- Posted via http://www.ruby-forum.com/.
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
