On Fri, May 13, 2011 at 2:52 AM, Fran <franm...@gmail.com> wrote: > 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. > > I can't think of much of a way around that, other than writing a utility to make it easier. Other people might have a better solution. In the best case, you have two developers with the same migration version number where their additions don't touch the same tables, and you can just pick an arbitrary one to be "31" and the other "32". In the worst case, you're going to have to merge the migrations together anyhow. (Well, I suppose the worst case is that they're entirely incompatible changes).
I could see this quickly becoming a huge pain even with just a few developers on a project... Unfortunately, I'm not familiar with much of anything that's designed to make this easier. What I tend to do is not even store migration info in version control for dev machines (opting instead to use data fixtures and ./app/console scripting), and then only use migrations to represent "release-point" changes to db schemas that are already live (doing backups, and running migrations via a fabric script). I've never tried this with a larger team of people, and it still has the problem of having to do manual merges sometimes (which, I think, is not really entirely avoidable), but I don't have to hork around with going up and down a migration chain and twiddling migration numbers. If anyone has a cleaner solution to this type of situation, I'd love to hear about it as well. -- 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
