test/dummy/db/schema.rb in dread-0.0.6 vs test/dummy/db/schema.rb in dread-0.0.7
- old
+ new
@@ -9,19 +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: 20140915161852) do
+ActiveRecord::Schema.define(version: 20140918223342) do
create_table "account_settings", force: true do |t|
t.string "time_zone"
t.integer "country_id"
t.datetime "created_at"
t.datetime "updated_at"
end
+ create_table "accounts", force: true do |t|
+ t.string "supplier_id"
+ t.string "account_number"
+ t.datetime "created_at"
+ t.datetime "updated_at"
+ end
+
create_table "comments", force: true do |t|
t.integer "tweet_id"
t.integer "user_id"
t.string "content"
t.datetime "created_at"
@@ -32,27 +39,52 @@
t.string "name"
t.datetime "created_at"
t.datetime "updated_at"
end
+ create_table "employees", force: true do |t|
+ t.string "name"
+ t.integer "manager_id"
+ t.datetime "created_at"
+ t.datetime "updated_at"
+ end
+
create_table "pictures", force: true do |t|
t.string "url"
t.integer "imageable_id"
t.string "imageable_type"
t.datetime "created_at"
t.datetime "updated_at"
end
+ create_table "suppliers", force: true do |t|
+ t.string "name"
+ t.datetime "created_at"
+ t.datetime "updated_at"
+ end
+
create_table "tweets", force: true do |t|
t.integer "user_id"
t.string "content"
t.datetime "created_at"
t.datetime "updated_at"
end
create_table "users", force: true do |t|
t.string "name"
t.string "email"
+ t.datetime "created_at"
+ t.datetime "updated_at"
+ end
+
+ create_table "wtf_ashtrays", force: true do |t|
+ t.string "color"
+ t.datetime "created_at"
+ t.datetime "updated_at"
+ end
+
+ create_table "wtf_cigarettes", force: true do |t|
+ t.string "brand"
t.datetime "created_at"
t.datetime "updated_at"
end
end