Migration in rails 2.1
May 28, 2008 – 12:25 amSome new migration feature in rails 2.1,
- Migration version number was keep trak in database, that means new rails was replace ’shema_info’ with a new table called ’schema migrations’.The old ’schema_info’ in Rails 2.0 just save the number of latest migration that has been execute but ’schema migrations’ table was created to keep trak which migration already execute. In Rails 2.0, sometimes if you are working with another rails developer in same project or merge the branch, they might created a higher migration number then you. So if you run db:migrate, your migration file won’t execute. With the new implement in Rails 2.1 they eliminate this problem.
- Change the structure of migration file. See the image below..how different with the Rails 2.0.
Awesome ya….
Popularity: 37% [?]
Tags: Rails, Rails 2.1, Ruby, Ruby On Rails
2 Responses to “Migration in rails 2.1”
How well does the new schema_migrations work with the old schema_info?
With a production DB of over 200 tables, what happens when we migrate?
Jim
[Reply]
By jim on Jun 8, 2008
You can refer here : http://dev.rubyonrails.org/ticket/11493
[Reply]
By lan on Jun 8, 2008