remove duplicate name

.github/workflows/master.yaml

@@ -17,6 +17,7 @@ jobs:
 #      - run: docker-compose run web bin/run-tests
       - uses: akhileshns/heroku-deploy@v3.12.13
         with:
+          branch: "master"
           heroku_email: ${{secrets.HEROKU_EMAIL}}
           heroku_api_key: ${{secrets.HEROKU_API_KEY}}
           heroku_app_name: "stadtratmonitor"

config/environments/development.rb

@@ -22,6 +22,8 @@ Rails.application.configure do
   # Raise an error on page load if there are pending migrations.
   config.active_record.migration_error = :page_load
 
+  config.active_record.legacy_connection_handling = false
+
   # Debug mode disables concatenation and preprocessing of assets.
   # This option may cause significant delays in view rendering with a large
   # number of complex assets.

db/migrate/20150413193656_create_papers.rb

@@ -1,7 +1,7 @@
 class CreatePapers < ActiveRecord::Migration[4.2]
   def change
     create_table :papers do |t|
-      t.string :name
+#      t.string :name
       t.string :url
       t.string :reference
       t.string :name

db/schema.rb

@@ -2,20 +2,19 @@
 # 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).
+# This file is the source Rails uses to define your schema when running `bin/rails
+# db:schema:load`. When creating a new database, `bin/rails db:schema:load` tends to
+# be faster and is potentially less error prone than running all of your
+# migrations from scratch. Old migrations may fail to apply correctly if those
+# migrations use external dependencies or application code.
 #
 # It's strongly recommended that you check this file into your version control system.
 
-ActiveRecord::Schema.define(version: 20151010070158) do
-
+ActiveRecord::Schema[7.0].define(version: 2015_10_10_070158) do
   create_table "importers", force: :cascade do |t|
     t.string "url"
-    t.datetime "created_at", null: false
-    t.datetime "updated_at", null: false
+    t.datetime "created_at", precision: nil, null: false
+    t.datetime "updated_at", precision: nil, null: false
   end
 
   create_table "paper_searches", force: :cascade do |t|
@@ -26,18 +25,18 @@ ActiveRecord::Schema.define(version: 20151010070158) do
   end
 
   create_table "papers", force: :cascade do |t|
-    t.string "name"
     t.string "url"
     t.string "reference"
+    t.string "name"
     t.string "body"
-    t.datetime "published_at"
-    t.datetime "scraped_at"
+    t.datetime "published_at", precision: nil
+    t.datetime "scraped_at", precision: nil
     t.string "paper_type"
     t.string "originator"
     t.text "resolution"
     t.text "content"
-    t.datetime "created_at"
-    t.datetime "updated_at"
+    t.datetime "created_at", precision: nil
+    t.datetime "updated_at", precision: nil
     t.index ["body"], name: "index_papers_on_body"
     t.index ["originator"], name: "index_papers_on_originator"
     t.index ["reference", "body"], name: "index_papers_on_reference_and_body", unique: true
@@ -46,8 +45,8 @@ ActiveRecord::Schema.define(version: 20151010070158) do
 
   create_table "users", force: :cascade do |t|
     t.string "email"
-    t.datetime "created_at"
-    t.datetime "updated_at"
+    t.datetime "created_at", precision: nil
+    t.datetime "updated_at", precision: nil
     t.index ["email"], name: "index_users_on_email", unique: true
   end