Content
View differences
Updated by Christian Rijke almost 13 years ago
Core migrations run in lexicographical order instead of numeric order as Rails3 removes leading 0s from the migration identifier (see screenshot).
Surprisingly, this wrong ordering doesn’t lead to issues for the core migrations themselves, but leads to problems as soon as other, newer migrations with the new timestamp format are added (eg. by installing them from plugins).
Surprisingly, this wrong ordering doesn’t lead to issues for the core migrations themselves, but leads to problems as soon as other, newer migrations with the new timestamp format are added (eg. by installing them from plugins).