purcell / renumber_migrations
watch download tarball
public
Forks0Right
Watchers1Right
Description: Rails plugin for renumbering clashing migrations in a project kept in svn
Homepage: http://www.sanityinc.com/articles/renumber-rails-migrations
Clone URL: git://github.com/purcell/renumber_migrations.git
Click here to lend your support to: renumber_migrations and make a donation at www.pledgie.com !
100644 43 lines (25 sloc) 1.392 kb
raw blame history 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

RenumberMigrations
==================
 
Automatically renumber new local migrations when their numbers clash with
team-mates' migrations updated from a subversion repository.
 
The plugin provides a rake task that has been used without problems for over
a year on a huge project with 8+ developers and over 600 migrations.
 
The plugin's home on the web is here:
 
   http://www.sanityinc.com/                                      - articles and news
   http://git.sanityinc.com/?p=renumber_migrations.git;a=summary  - code and downloads
 
Send feedback or patches by email to steve@sanityinc.com
 
 
Examples
========
 
You're working on migration 045_add_my_new_feature.rb, when one of your team-mates checks
045_some_other_migration.rb into svn.  You notice the numbering clash (or 'rake db:migrate'
notices it for you), and you simply run the db:migrate:renumber task:
 
% rake db:migrate:renumber
 
Voilá - your migration is renumbered to 046, and the database schema is left at version
044 ready for you to re-test your migration.
 
 
Requirements
============
 
Note that renumbering a migration *requires* that you have a working #down method for
your migration.
 
Renumbering also requires that you have network access to the subversion server, since
clashing migrations are temporarily removed locally, and later re-requested.
 
 
 
Copyright (c) 2007 Steve Purcell, released under the MIT license