# During upgrade, schema\_migrations table not populated

**URL:** <https://www.ruby-forum.com/t/during-upgrade-schema-migrations-table-not-populated/176902>\
**Category:** Rails\
**Created:** [October 7, 2009, 9:34pm UTC](https://www.ruby-forum.com/t/during-upgrade-schema-migrations-table-not-populated/176902 "2009-10-07T21:34:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![terrii](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/a587f6/32.png) [@terrii](https://www.ruby-forum.com/u/terrii)\
**Post date:** [October 7, 2009, 9:34pm UTC](https://www.ruby-forum.com/t/during-upgrade-schema-migrations-table-not-populated/176902/1 "2009-10-07T21:34:58Z")

</div>

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??