fix module progression migrations

test plan: - migrations should run successfully, specifically - 20140418210000 - 20140418211204 - migrations should run predeploy Change-Id: I764f996be7d7da350a3e88e702d1578979d7523d Reviewed-on: https://gerrit.instructure.com/35245 Reviewed-by: Cody Cutrer <[email protected]> Tested-by: Jenkins <[email protected]> Product-Review: Cody Cutrer <[email protected]> QA-Review: Cody Cutrer <[email protected]>
Dunnzilla · May 21, 2014 · 041c9b8 · 041c9b8
1 parent 8178266
commit 041c9b8
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 2 deletions.
diff --git a/db/migrate/20140418210000_populate_lock_version_on_context_module_progressions.rb b/db/migrate/20140418210000_populate_lock_version_on_context_module_progressions.rb
@@ -1,5 +1,5 @@
 class PopulateLockVersionOnContextModuleProgressions < ActiveRecord::Migration
-  tag :postdeploy
+  tag :predeploy
 
   def self.up
     DataFixup::PopulateLockVersionOnContextModuleProgressions.run

diff --git a/db/migrate/20140418211204_disallow_null_on_context_module_progression_lock_version_column.rb b/db/migrate/20140418211204_disallow_null_on_context_module_progression_lock_version_column.rb
@@ -2,7 +2,6 @@ class DisallowNullOnContextModuleProgressionLockVersionColumn < ActiveRecord::Mi
   tag :predeploy
 
   def self.up
-    ContextModuleProgression.where(lock_version: nil).update_all(lock_version: 0)
     change_column_null :context_module_progressions, :lock_version, false
   end