spec/dummy/db/schema.rb in money-rails-1.3.0 vs spec/dummy/db/schema.rb in money-rails-1.4.0

@@ -9,20 +9,20 @@
 # 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: 20150126231442) do
+ActiveRecord::Schema.define(version: 20150303222230) do
 
-  create_table "dummy_products", force: true do |t|
+  create_table "dummy_products", force: :cascade do |t|
     t.string   "currency"
     t.integer  "price_cents"
     t.datetime "created_at"
     t.datetime "updated_at"
   end
 
-  create_table "products", force: true do |t|
+  create_table "products", force: :cascade do |t|
     t.integer  "price_cents"
     t.integer  "discount"
     t.datetime "created_at"
     t.datetime "updated_at"
     t.integer  "bonus_cents"
@@ -34,19 +34,22 @@
     t.integer  "aliased_cents"
     t.integer  "delivery_fee_cents"
     t.integer  "restock_fee_cents"
     t.integer  "reduced_price_cents"
     t.string   "reduced_price_currency"
+    t.integer  "special_price_cents"
+    t.integer  "lambda_price_cents"
+    t.string   "skip_validation_price_cents"
   end
 
-  create_table "services", force: true do |t|
+  create_table "services", force: :cascade do |t|
     t.integer  "charge_cents"
     t.integer  "discount_cents"
     t.datetime "created_at"
     t.datetime "updated_at"
   end
 
-  create_table "transactions", force: true do |t|
+  create_table "transactions", force: :cascade do |t|
     t.integer  "amount_cents"
     t.integer  "tax_cents"
     t.string   "currency"
     t.datetime "created_at"
     t.datetime "updated_at"