You didn’t actually add any commentary with that excerpt so I can only guess at your point. Perhaps you’re saying that you agree with that comment?

I suppose I agree with it too, IF you aren’t using any database features that would be omitted by db:schema:dump (schema.rb) or db:structure:dump (schema.sql). And that’s a pretty big “if”. I even capitalized it! :)

The nice thing about migrations is that even if you dare to use Rails on a project where those opinionated-software decisions don’t happen to fit 100% with your project, you can use still use migrations to build the DB from scratch or incrementally in a reliable and repeatable fashion. Just throw a few raw SQL DDL statements in a migration and put the reverse transformation in the down method, and you’re all set.

# 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 to check this file into your version control system.