This project is archived and is in readonly mode.
rake db:forward (opposite of db:rollback)
This patch adds a db:forward rake task that mimics db:rollback, except with movement in the opposite direction. The default action is to perform only the next migration. The STEP variable is also available to perform a variable number of steps.
Examples:
Perform the next migration... rake db:forward
Perform ONLY the next 4 migrations.... rake db:forward STEP=4
-
migrate_forward.diff
2.08 KB
-
-
CancelProfileIsBroken- Tag changed from migrations, patch to bugmash, migrations, patch
-
-
Rizwan Reza- Assigned user set to José Valim
- Tag changed from bugmash, migrations, patch to bugmash, migrations, patch, tested, verified
verified patch
+1 This works. Tests passing under 2-3-stable. Patch doesn't apply in master.
-
José Valim- Assigned user changed from José Valim to Pratik
- State changed from incomplete to new
I'm handling just master tickets. :) Assigning to Pratik.
-
Repository
- State changed from new to resolved
(from [7f84f14efabf3e342a231b8aa9650cb484c802d6]) Add rake db:forward - opposite of db:rollback [#768 rake db:forward (opposite of db:rollback) state:resolved]
Example:
rake db:forward # performs the next migration rake db:forward STEP=4 # performs the next 4 migrationsSigned-off-by: Pratik Naik pratiknaik@gmail.com
http://github.com/rails/rails/commit/7f84f14efabf3e342a231b8aa9650c... -
CancelProfileIsBroken
- Assigned user cleared.
- Tag changed from bugmash, migrations, patch, tested, verified to migrations, patch, tested, verified
- Milestone cleared.