fix migration

Author: glabrat

config.ru

@@ -0,0 +1,4 @@
+# config.ru
+
+require './app'
+run Sinatra::Application

db/migrate/20180518224016_create_partners.rb

@@ -3,9 +3,10 @@ def self.up
     create_table :partners do |t|
       t.string :name
       t.string :last_name
-      t.integer :rut, unique: true
+      t.integer :rut
       t.timestamps
     end
+    add_index :partners, :rut, unique: true
   end
 
   def self.down

db/schema.rb

@@ -0,0 +1,27 @@
+# This file is auto-generated from the current state of the database. Instead
+# of editing this file, please use the migrations feature of Active Record to
+# incrementally modify your database, and then regenerate this schema definition.
+#
+# Note that this schema.rb definition is the authoritative source for your
+# database schema. If you need to create the application database on another
+# system, you should be using db:schema:load, not running all the migrations
+# 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: 2018_05_18_224016) do
+
+  # These are extensions that must be enabled in order to support this database
+  enable_extension "plpgsql"
+
+  create_table "partners", force: :cascade do |t|
+    t.string "name"
+    t.string "last_name"
+    t.integer "rut"
+    t.datetime "created_at", null: false
+    t.datetime "updated_at", null: false
+    t.index ["rut"], name: "index_partners_on_rut", unique: true
+  end
+
+end