I agree with your comments.

I would like to add that using Rails to maintain database schema helps the developers to eliminate that “one more thing” to do.

Migrations are such a clean way to be able to roll database schemas forward and backward, as well as to be able to tie database schema versions with code versions in the code repository.

Projects that don’t do this will often have the problem where they can restore a past version of the code, but not have any idea what the corresponding database schema was.