schema_statements#initialize_schema_migrations_table does not respect config.active_record.table_name_prefix

On second thought, I'm not sure it has anything to do with config.active_record.table_name_prefix. I had a custom rake task that was mucking with the table_name_prefix. Removing the task causes the error message to change to

SQLite3::SQLException: index unique_schema_migrations already exists: CREATE UNIQUE INDEX "unique_schema_migrations" ON "ts_schema_migrations" ("version")

That is, there's simply something wrong with trying to re-create the schema migrations index.

Possibly related to #1543 index "unique_schema_migrations" should use table prefix/suffix (which includes a patch); that unique_schema_migrations index should use the table prefix in it's name.

Digging a little further...

The reason I added the custom rake task to muck with table_name_prefix is that rake db:migrate honored table_name_prefix. That is, the task (a) created tables in the development environment with the prefix and (b) created a schema.rb file with the prefixes. Then, when I ran rake db:test:load, it, too, honored the prefix, causing double prefixes.

If db:test:load is going to honor table_name_prefix (which is should, since otherwise it gets the unique_schema_migrations index wrong), db:migrate should NOT put prefixes into schema.rb.