>> To me there seem to be 3 possible orders: C-E-D, C-D-E, E-C-D. > > Then in that edge case, you simply modify either migrations > themselves, or the timestamp, so that the order is correct.
I don't think that two developers working in parallel can be considered and edge case, and being that a common case in my workplace is that we decided to switch to cake schema (after I stoped of pulling my hair and got them working), since them we are a happy team. > One of the best things about Migrations, is that they are fully > incremental, and each one can be rolled back very easily. I do agree, doing changes in a incremental (and atomic) way really helps to do agile development. > It's all sounding to me that this is all about preference. All I know > is that the core team plan on reviewing Schema and Migrations after > 1.2 is released, to see if there is an common ground. I certainly hope > we can do something, as there is a lot of overlay between the two. That would be great, there are a lot of place for improvement an innovation in the field. > But > if Migrations is not used, then I will simply continue to use and > develop it as third party add-on for Cake. Don't know what to say, but I get used to split emails in chunks.... :O Cheers, - Dardo Sordi. > FYI: Migrations v4.0 Beta has just been released -> > http://developingwithstyle.com/2008/05/20/cakephp-migrations-v40-beta/ > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
