Running down migrations based on run_on column #156
Description
We have run into some situations where the current method of running down migrations (based on the migration's name) is not desirable, since the migrations were created in a different order from which they were applied.
It would be nice to have an option where 'down' migrations are run based on the value of the 'run_on' column, rather than the lexical order of the migration name.