Ticket #926 (closed enhancement: wontfix)
Option to use timestamp migrations rather than serial number
|Reported by:||msabramo@…||Owned by:||andrew|
The serial numbers work great most of the time, but we recently ran into a fair amount of trouble when multiple developers were changing (different) models in a project on different branches. Because each developer is on a branch and doesn't see the migrations that developers on other branches are generating, it is extremely easy for the serial numbers to collide and then it's a mess to sort through after merging.
Timestamped migrations don't completely eliminate the problems with working on multiple branches -- differing frozen ORM state is also a problem, but they at least make it easier to see what happened and to sort through the migrations a bit more easily.
Since this is a huge change in how South works, I would implement this as an option that defaults to False.