test/dummy/db/schema.rb in dj_dashboard-0.0.5 vs test/dummy/db/schema.rb in dj_dashboard-0.0.6

@@ -9,11 +9,11 @@
 # 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 to check this file into your version control system.
 
-ActiveRecord::Schema.define(:version => 20111212042040) do
+ActiveRecord::Schema.define(:version => 20111213032010) do
 
   create_table "delayed_jobs", :force => true do |t|
     t.integer  "priority",   :default => 0
     t.integer  "attempts",   :default => 0
     t.text     "handler"
@@ -22,10 +22,16 @@
     t.datetime "locked_at"
     t.datetime "failed_at"
     t.string   "locked_by"
     t.datetime "created_at"
     t.datetime "updated_at"
+    t.string   "job_name"
   end
 
-  add_index "delayed_jobs", ["priority", "run_at"], :name => "delayed_jobs_priority"
+  add_index "delayed_jobs", ["failed_at", "attempts"], :name => "index_delayed_jobs_on_failed_at_and_attempts"
+  add_index "delayed_jobs", ["failed_at"], :name => "index_delayed_jobs_on_failed_at"
+  add_index "delayed_jobs", ["job_name"], :name => "index_delayed_jobs_on_job_name"
+  add_index "delayed_jobs", ["locked_at", "failed_at"], :name => "index_delayed_jobs_on_locked_at_and_failed_at"
+  add_index "delayed_jobs", ["locked_at"], :name => "index_delayed_jobs_on_locked_at"
+  add_index "delayed_jobs", ["priority", "run_at"], :name => "altered_delayed_jobs_priority"
 
 end