> He addresses the answer in that post. You don't label the migration
> sequentially. You label it based on UTC timestamp as the race
> condition where 2 developers generate a migration at exactly the same
> moment is highly unlikely. Rails 2.1 is going that way (http://
> railscasts.com/episodes/107).
If you are talking about a parallel development environment, a change
made forward in time doesn't necessarily should be ordered after
others that happened before it but based on the same revision.
C --- D
/ \
A---B------E-------*--- Should migration E be between C and D ? Can we
say that based on the timestamp?
You'll see, some times order matters.
To me there seem to be 3 possible orders: C-E-D, C-D-E, E-C-D.
- Dardo Sordi.
> - Keith
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
