Distinguish same foreign key constraint on multiple columns

[nagamoto]

When there are multiple constraints that refer to the same data in one table,
Ridgepole cannot distinguish between the two constraints and considers them as duplicate operations, and an error occurs.

e.g.

ActiveRecord::Schema.define(version: 2019_07_11_071444) do

  create_table "direct_messages", options: "ENGINE=InnoDB DEFAULT CHARSET=utf8", force: :cascade do |t|
    t.bigint "sender_id"
    t.bigint "reciever_id"
    t.text "body"
    t.datetime "created_at", null: false
    t.datetime "updated_at", null: false
    t.index ["reciever_id"], name: "index_direct_messages_on_reciever_id"
    t.index ["sender_id"], name: "index_direct_messages_on_sender_id"
  end

  create_table "users", options: "ENGINE=InnoDB DEFAULT CHARSET=utf8", force: :cascade do |t|
    t.string "email"
    t.datetime "created_at", null: false
    t.datetime "updated_at", null: false
  end

  add_foreign_key "direct_messages", "users", column: "reciever_id"
  add_foreign_key "direct_messages", "users", column: "sender_id"
end

Therefore, This PR makes Ridgepole distinguish from column name options as foreign key constraints.

Thanks for your great product.

Additional Information

• CMD: bundle exec ridgepole -c config/database.yml --export --output d… nagamoto/sample-rails-app#1
• CMD: bundle exec ridgepole -c config/database.yml --export --output d… nagamoto/sample-rails-app#2

*These link destinations are written in Japanese

[winebarrel]

Thank you!

[winebarrel]

v0.7.8 has been released.