Avoid relying on the order in which emails are sent

[rails.git] / db / migrate / 024_order_relation_members.rb

diff --git a/db/migrate/024_order_relation_members.rb b/db/migrate/024_order_relation_members.rb
index 76ec32222237ef32649849426140aa9b9cd0022e..fbb276dd57672ee40fe68d9b75aab69cd1e655dc 100644 (file)
--- a/db/migrate/024_order_relation_members.rb
+++ b/db/migrate/024_order_relation_members.rb
@@ -1,4 +1,4 @@
-require 'lib/migrate'
+require "migrate"
 
 class OrderRelationMembers < ActiveRecord::Migration
   def self.up
@@ -7,12 +7,12 @@ class OrderRelationMembers < ActiveRecord::Migration
     add_column(:relation_members, :sequence_id, :integer,
                :default => 0, :null => false)
 
-    # update the sequence column with default (partial) ordering by 
+    # update the sequence column with default (partial) ordering by
     # element ID. the sequence ID is a smaller int type, so we can't
     # just copy the member_id.
     execute("update relation_members set sequence_id = mod(member_id, 16384)")
 
-    # need to update the primary key to include the sequence number, 
+    # need to update the primary key to include the sequence number,
     # otherwise the primary key will barf when we have repeated members.
     # mysql barfs on this anyway, so we need a single command. this may
     # not work in postgres... needs testing.