Thanks for answering, Yes, each developer works in his own database in his dev machine. The problem is that if we are in migrate version 30 for example and each developer makes changes in the database, each developer would have migrate version 31 and when we merge the branches we have to fix this "manually". So my question were if there is any method to deal with that or how do you do that.
On 12 mayo, 17:58, Jeremiah Dodds <jeremiah.do...@gmail.com> wrote: > On Thu, May 12, 2011 at 6:00 AM, Fran <franm...@gmail.com> wrote: > > Hi! > > > I have a Symfony project with Git and we are three developers, two of > > us are working on a develop branch and the other one is working in a > > new branch with new features, the problem is the changes in the > > database and the generation of migration versions, how can we deal > > with that? I mean, when we worked in the same branch we talked between > > us when we were going to change something in the schema.yml, but in > > the new branch we don't want to have the changes in develop until the > > features are done. > > I hope I have explaned. > > Are you working on the same database? If so, developers should probably work > with their own databases on their dev machines. If not, I'm not sure what > the issue is, as you should be able to merge any schema / migration changes > (although that might be a little bit of a pain with migration changes / > versions) -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en