Patch #6527
Recent migrations don't have the correct date
| Status: | Closed | Start date: | 2010-09-29 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: |  Eric Davis | % Done: | 0% | |
| Category: | Code cleanup/refactoring | |||
| Target version: | - |
Description
Migrations added in r4216 don't have the correct name (201001 instead of 201009). db:migrate run fine but the schema version reported with ruby script/about is somehow incorrect. It has no consequence until someone report an issue and we don't know if his database is up to date. It shouldn't be a problem if we plan to have other migrations in a near future.
Eric: I let you decide if it should be changed or not.
Related issues
History
#1
Updated by Eric Davis almost 10 years ago
- Status changed from New to Closed
Shouldn't matter since Rails understands how to apply older migrations. Also if we change them now, we would have to have some patch for people with the older migrations already to make sure they don't run twice.