# Migrations + Teams + possible SVN Conflicts

**URL:** <https://www.ruby-forum.com/t/migrations-teams-possible-svn-conflicts/123762>\
**Category:** Rails\
**Created:** [December 20, 2007, 12:56pm UTC](https://www.ruby-forum.com/t/migrations-teams-possible-svn-conflicts/123762 "2007-12-20T12:56:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![adityasanghi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/bbce88/32.png) [@adityasanghi](https://www.ruby-forum.com/u/adityasanghi)\
**Post date:** [December 20, 2007, 12:56pm UTC](https://www.ruby-forum.com/t/migrations-teams-possible-svn-conflicts/123762/1 "2007-12-20T12:56:03Z")

</div>

Hi Guys,

I’ve got a team of people working on a Rails Project. They work  
independently on various different modules. Each sub team/developer  
creates relevant migrations for the component they work on and then  
check-in. There are no conflicts as well since they all add new  
migration files. However we end up with multiple migrations with the  
same migration number. What is the ways other Rails team avoid this  
problem?

Cheers,  
Aditya

---

<div class="post-metadata">

**Author:** ![adityasanghi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/bbce88/32.png) [@adityasanghi](https://www.ruby-forum.com/u/adityasanghi)\
**Post date:** [December 20, 2007, 8:56pm UTC](https://www.ruby-forum.com/t/migrations-teams-possible-svn-conflicts/123762/2 "2007-12-20T20:56:00Z")

</div>

We announce that we’re creating a migration number x to the other  
members of  
the team and the other members keep this in mind when creating new  
migrations.

On Dec 20, 2007 10:26 PM, Aditya S.  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> ## Cheers, Aditya
> 
> Posted via [http://www.ruby-forum.com/](http://www.ruby-forum.com/).
> 
> >

–  
Ryan B.

> **[frozenplague.net](http://www.frozenplague.net)**
>
> This domain may be for sale!

---

<div class="post-metadata">

**Author:** ![adityasanghi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/bbce88/32.png) [@adityasanghi](https://www.ruby-forum.com/u/adityasanghi)\
**Post date:** [December 20, 2007, 9:18pm UTC](https://www.ruby-forum.com/t/migrations-teams-possible-svn-conflicts/123762/3 "2007-12-20T21:18:52Z")

</div>

> > Hi Guys,
> > 
> > I’ve got a team of people working on a Rails Project. They work  
> > independently on various different modules. Each sub team/developer  
> > creates relevant migrations for the component they work on and then  
> > check-in. There are no conflicts as well since they all add new  
> > migration files. However we end up with multiple migrations with the  
> > same migration number. What is the ways other Rails team avoid this  
> > problem?

There was a plugin just released to help with this (by renumbering them)  
but I can’t for the life of me remember the name.

---

<div class="post-metadata">

**Author:** ![adityasanghi](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/bbce88/32.png) [@adityasanghi](https://www.ruby-forum.com/u/adityasanghi)\
**Post date:** [December 21, 2007, 12:37am UTC](https://www.ruby-forum.com/t/migrations-teams-possible-svn-conflicts/123762/4 "2007-12-21T00:37:15Z")

</div>

This is a special case for our team, too. We just broadcast that  
there’s a new migration, and try to get it checked in before all the  
other changes. In the event of a collision, the person with the last  
check-in just renames the migration. SVN renaming is easy (I am still  
recovering from post-traumatic stress related to many years of CVS  
use).

We had thought this might go away when we all started to work off the  
same central development database (assuming that the migrate task got  
its number from the schema version table), but it seems to be just  
scanning the migration files.

Tom