queries are executed in reverse order during a rollback

[robacarp]

This may not be a bug, but I found it counter intuitive. If it isn't a bug, it's behavior I found undocumented.

This migration assumes the existence of a table, and drops it. On rollback, it creates the table and an associated index.

-- +migrate Up
DROP TABLE routes;
-- SQL in section 'Up' is executed when this migration is applied

-- +migrate Down
CREATE TABLE routes(
  id BIGSERIAL PRIMARY KEY,
  foreign_key BIGINT,
);

CREATE INDEX routes_foreign_key_idx ON routes (foreign_key);
-- SQL section 'Down' is executed when this migration is rolled back

When executing #down on a migrator, this migration will fail because the table doesn't exist when the 'create index' is executed. I believe this is because statement order is reversed during a rollback.