Ruby on Rails | Screencasts | Download | Documentation | Weblog | Community | Source

Ticket #11483 (reopened defect)

Opened 2 months ago

Last modified 2 months ago

[BUG] Multiple migraions with the same migration number

Reported by: timurv Assigned to: core
Priority: normal Milestone: 2.x
Component: Railties Version: edge
Severity: normal Keywords:
Cc:

Description

Assume we generate several migrations, after using utc based style all migration will have same number.

Maybe migration_template should check next migration number again, and increment seconds?

Change History

(in reply to: ↑ description ) 03/31/08 15:31:44 changed by broughcut

  • component changed from Railties to ActiveRecord.

This change also frustrates tab auto-completion when opening migration files. Appending the utc timestamp to an incrementing version number would eliminate any possibility of local collisions and allow tab completion as before.

03/31/08 15:37:06 changed by broughcut

  • component changed from ActiveRecord to Railties.

03/31/08 21:51:04 changed by Henrik N

  • status changed from new to closed.
  • resolution set to worksforme.

[9122] made migrations use timestamps.

03/31/08 21:53:50 changed by Henrik N

Or did you mean there is an issue with the timestamp migrations? The error report isn't too clear.

03/31/08 22:06:58 changed by timurv

  • status changed from closed to reopened.
  • resolution deleted.

Yes, this ticket about migrations with utc migration numbers.

For example: we create generator that generates several migrations at one time. That means all migrations will have same migration number -- datetime when we run generator.