This project is archived and is in readonly mode.
Use Rails 3.1 `change` method in migration and model generators
Reported by Prem Sichanugrist (sikachu) | December 31st, 2010 @ 06:25 PM | in 3.1
I saw that Aaron has done a great job on implementing
migration's change
method. So, I think we should use
that in Rails 3.1 generators by default.
I've attached the patch with modified test cases, which it's
passing on the current master
. This patch should only
be applied to master
.
Thank you :)
Comments and changes to this ticket
-
Prem Sichanugrist (sikachu) January 1st, 2011 @ 08:23 PM
Add a test case to make sure that
rake db:migrate
still run fines after we change it to usechange
method. -
Aaron Patterson January 4th, 2011 @ 07:37 PM
- State changed from new to committed
Applied, thanks!
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>