Added migration to remove is_available_to_prime (zero-down migration)

transcom · Jun 2, 2020 · 650fce6 · 650fce6
1 parent 62a55fb
commit 650fce6
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 0 deletions.
diff --git a/migrations/app/migrations_manifest.txt b/migrations/app/migrations_manifest.txt
@@ -511,3 +511,4 @@
 20200513151500_uploader_refactor_zero_down_alter_tables.up.sql
 20200515202122_payment_service_item_nullable_price.up.sql
 20200527145249_add_mto_available_timestamp.up.sql
+20200602144311_remove_is_available_to_prime.up.sql
diff --git a/migrations/app/schema/20200602144311_remove_is_available_to_prime.up.sql b/migrations/app/schema/20200602144311_remove_is_available_to_prime.up.sql
@@ -0,0 +1,11 @@
+-- Zero-down migrations (for a later PR/deployment)
+
+-- This is just meant to catch any older code that may have changed the old
+-- field during the previous deployment.
+UPDATE move_task_orders
+SET available_to_prime_at = updated_at
+WHERE is_available_to_prime = true
+  AND available_to_prime_at IS NULL;
+
+ALTER TABLE move_task_orders
+    DROP COLUMN is_available_to_prime;