[url]http://www.activars.com/tags/migration[/url]
Posted by jay
Rails use a UTC time stamp as migration version by default. Although most examples in books have simple number based system for managing migration versions, there isn’t much information about version type configuration. By default, a migration file(>=Rail 2.0) name look similar to:
20081202130543_create_group_categories.rb
We can turn this off and use numeric prefixes by adding this in config/environment.rb
config.active_record.timestamped_migrations = false
New generated file name will look like:
003_create_group_categories.rb
But bare in mind, if the Rails project is getting large and a few developers are working on same project, it’s likely that two developers generate same version of migration (e.g. 003). Using time stamp is introduced since Rail 2.0 to avoid such problem. So… better keep the default setting!
Posted by jay
Rails use a UTC time stamp as migration version by default. Although most examples in books have simple number based system for managing migration versions, there isn’t much information about version type configuration. By default, a migration file(>=Rail 2.0) name look similar to:
20081202130543_create_group_categories.rb
We can turn this off and use numeric prefixes by adding this in config/environment.rb
config.active_record.timestamped_migrations = false
New generated file name will look like:
003_create_group_categories.rb
But bare in mind, if the Rails project is getting large and a few developers are working on same project, it’s likely that two developers generate same version of migration (e.g. 003). Using time stamp is introduced since Rail 2.0 to avoid such problem. So… better keep the default setting!
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
