summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormo khan <mo.khan@gmail.com>2020-06-13 09:33:10 -0600
committermo khan <mo.khan@gmail.com>2020-06-13 09:34:57 -0600
commit8e136a60dba83dd458a76de9e9d5e6b9e0426094 (patch)
treecb197ccdb63fd6f8510b3397c8b4309e4424b9e3
parent46bc7b9967b2a09dc414f6a14003541c0e32cdc7 (diff)
Update to new header
-rw-r--r--db/schema.rb10
1 files changed, 5 insertions, 5 deletions
diff --git a/db/schema.rb b/db/schema.rb
index f978614..ea3d5cb 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.