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 -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
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 Sanghi <rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote:> > 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 > -- > Posted via http://www.ruby-forum.com/. > > > >-- Ryan Bigg http://www.frozenplague.net --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
>> 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. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---