This project is archived and is in readonly mode.
[PATCH] Which are they `migration version'? or `migration number'?
Reported by Yuya.Nishida. | August 17th, 2009 @ 10:42 AM | in 3.0.2
migration version' and
migration number' means same
thing, I think. But the source code comments and guides uses both
words, so it is ambiguous.
These patches are unifying migration number'
in
migration version' or unifying migration version'
in
migration number'.
Either of them resolves ambiguous definition.
Please choose them, and apply it, please.
Comments and changes to this ticket
-
Rizwan Reza March 26th, 2010 @ 09:09 AM
- State changed from new to open
- Assigned user set to Rizwan Reza
- Milestone cleared.
Hey Yuya,
Can you provide an updated patch for master branch using migration version?
Thanks.
-
Rizwan Reza March 28th, 2010 @ 08:47 AM
- State changed from open to resolved
Just committed to docrails.
-
Rizwan Reza April 3rd, 2010 @ 08:17 PM
- State changed from resolved to committed
(from [155f0be16ba4600e61e331b00e67d281e0550172]) Changes migration number to version due to ambiguity. [#3065 state:committed] http://github.com/rails/rails/commit/155f0be16ba4600e61e331b00e67d2...
-
Jeremy Kemper October 15th, 2010 @ 11:01 PM
- Milestone set to 3.0.2
- Importance changed from to Low
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Attachments
Tags
Referenced by
- 3065 [PATCH] Which are they `migration version'? or `migration number'? (from [155f0be16ba4600e61e331b00e67d281e0550172]) Changes...