spec/dummy/db/schema.rb in ar-translatable-0.1.0 vs spec/dummy/db/schema.rb in ar-translatable-0.2.0

@@ -9,26 +9,26 @@
 # from scratch. The latter is a flawed and unsustainable approach (the more migrations
 # you'll amass, the slower it'll run and the greater likelihood for issues).
 #
 # It's strongly recommended that you check this file into your version control system.
 
-ActiveRecord::Schema.define(version: 20140625174008) do
+ActiveRecord::Schema.define(version: 20_140_625_174_008) do
 
-  create_table "translated_words", force: true do |t|
-    t.string   "translatable_type", null: false
-    t.integer  "translatable_id",   null: false
-    t.string   "key",               null: false
-    t.string   "locale",            null: false
-    t.string   "value",             null: false
-    t.datetime "created_at"
-    t.datetime "updated_at"
+  create_table 'translated_words', force: true do |t|
+    t.string 'translatable_type', null: false
+    t.integer 'translatable_id',   null: false
+    t.string 'key',               null: false
+    t.string 'locale',            null: false
+    t.string 'value',             null: false
+    t.datetime 'created_at'
+    t.datetime 'updated_at'
   end
 
-  add_index "translated_words", ["translatable_type", "translatable_id", "key", "locale"], name: "translated_word", unique: true
+  add_index 'translated_words', %w(translatable_type translatable_id key locale), name: 'translated_word', unique: true
 
-  create_table "users", force: true do |t|
-    t.date     "birthday"
-    t.datetime "created_at"
-    t.datetime "updated_at"
+  create_table 'users', force: true do |t|
+    t.date 'birthday'
+    t.datetime 'created_at'
+    t.datetime 'updated_at'
   end
 
 end