Migrations in Rails 2.1 - HowFlow

Most Recent | 24 hours | 7 days | 30 days | 365 days |

3
Vote

Migrations in Rails 2.1 External Link

Category: Ruby on Rails | Tags: rails railscasts migration

2 Comments

railscasts.com — If you like it or not, migrations now have a timestamp as their version number in Rails 2.1. In this Railscasts episode Ryan Bates explains this change and shows you some other cool additions.

Posted by

flood 7 months ago

Comments

written by twan 7 months

Nice, but does not really fix my problems with migrations, which are more migrations which bail out while migrating and leave the database in a inconsistent state or assitance for migrating a live database in smaller transactions. Think makes it even worse, because there seems no fixed order more for migrations. What happens if developer #1 deletes a row which an developer #2 wants to rename with another migration. Before you did get at least an error that there is something wrong with your database version...

written by aroedl 7 months

That's exactly what I was thinking when I saw the transition to the timestamp-based migration naming for the first time. I still don't get the advantage of the new system, but time will tell.

Please login to comment.