Correct google webmaster tools bug.

[rails.git] / db / migrate / 025_add_end_time_to_changesets.rb

diff --git a/db/migrate/025_add_end_time_to_changesets.rb b/db/migrate/025_add_end_time_to_changesets.rb
index 553fd9e2ac9a48ae0a7d69b8d6af5766e1368332..20d66719df800384a2a708a83cdda4b0fcb172ee 100644 (file)
--- a/db/migrate/025_add_end_time_to_changesets.rb
+++ b/db/migrate/025_add_end_time_to_changesets.rb
@@ -1,3 +1,5 @@
+require 'lib/migrate'
+
 class AddEndTimeToChangesets < ActiveRecord::Migration
   def self.up
     # swap the boolean closed-or-not for a time when the changeset will
@@ -7,8 +9,8 @@ class AddEndTimeToChangesets < ActiveRecord::Migration
     # it appears that execute will only accept string arguments, so
     # this is an ugly, ugly hack to get some sort of mysql/postgres
     # independence. now i have to go wash my brain with bleach.
-    #execute("update changesets set closed_at=(now()-'1 hour') where open=(1=0)")
-    #execute("update changesets set closed_at=(now()+'1 hour') where open=(1=1)")
+    execute("update changesets set closed_at=(now()-#{interval_constant('1 hour')}) where open=(1=0)")
+    execute("update changesets set closed_at=(now()+#{interval_constant('1 hour')}) where open=(1=1)")
 
     # remove the open column as it is unnecessary now and denormalises 
     # the table.