Migrations + Teams + possible SVN Conflicts

Rails
1

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

2

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.
[email protected]
wrote:

Cheers,
Aditya

Posted via http://www.ruby-forum.com/.

–
Ryan B.

3

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.

4

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