test/dummy/db/schema.rb in myreplicator-0.0.16 vs test/dummy/db/schema.rb in myreplicator-0.0.17

- old
+ new

@@ -9,12 +9,17 @@ # 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 => 20121115194022) do +ActiveRecord::Schema.define(:version => 20121213003553) do + create_table "my_test", :force => true do |t| + t.string "desc", :limit => 45 + t.datetime "updated_at" + end + create_table "myreplicator_exports", :force => true do |t| t.string "source_schema" t.string "destination_schema" t.string "table_name" t.string "incremental_column" @@ -26,20 +31,32 @@ t.string "cron" t.string "state", :default => "new" t.text "error" t.boolean "active", :default => true t.integer "exporter_pid" - t.integer "transporter_pid" - t.integer "loader_pid" t.datetime "export_started_at" t.datetime "export_finished_at" - t.datetime "load_started_at" - t.datetime "load_finished_at" - t.datetime "transfer_started_at" - t.datetime "transfer_finished_at" t.datetime "created_at", :null => false t.datetime "updated_at", :null => false end add_index "myreplicator_exports", ["source_schema", "destination_schema", "table_name"], :name => "unique_index", :unique => true + + create_table "myreplicator_logs", :force => true do |t| + t.integer "pid" + t.string "job_type" + t.string "name" + t.string "file" + t.string "state" + t.string "thread_state" + t.string "hostname" + t.string "export_id" + t.text "error" + t.text "backtrace" + t.string "guid" + t.datetime "started_at" + t.datetime "finished_at" + t.datetime "created_at", :null => false + t.datetime "updated_at", :null => false + end end