From fc8e22b82e49329e7476e1119fe0f87594f5435b Mon Sep 17 00:00:00 2001 From: Maikel Linke Date: Wed, 9 Jun 2021 16:02:05 +1000 Subject: [PATCH] Update schema file description I ran `rake db:migrate` and Rails updated this section. Let's use or we have to constantly checkout the schema after migrations or we'll have unrelated changes in future pull requests. --- db/schema.rb | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/db/schema.rb b/db/schema.rb index 2a16f4a7d7..6f9820c6b4 100644 --- a/db/schema.rb +++ b/db/schema.rb @@ -2,11 +2,11 @@ # 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 `rails +# db:schema:load`. When creating a new database, `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.