Currently no support for indexes that utilize `STORING`

[MarcusRiemer]

Currently it is only possible to specify the columns that need to be stored in an index using the regular add_index method. We therefore resort to execute statements like the following:

CREATE INDEX "users_lastname_asc"
ON users (last_name ASC)
STORING (first_name, company_id);

This will however add an index declaration to the schema.rb that reads as follow:

t.index ["last_name", "first_name", "company_id"], name: "users_lastname_asc"

This seems like an implementation detail leaking into the schema.rb: Obviously the stored columns are part of the index, but to the best of my understanding they are not contributing to the lookup data structures. So the schema.rb is now expressing something different than the actual migration.

tl;dr: Please ...

• Support STORING in add_index
• Support indices created using STORING in schema.rb