nearinfinity/node-db-migrate — Issue #3: order is not guaranteed when running migration statements
Author: joeferner
Created: 2011-12-15 17:42:43+00:00
State: open

Example. If I have a table named "people" and my migration tries to drop the table and then recreate it I would expect that to work. Instead I get a people table already exists error.

to fix this maybe all sql statements should be queued up and executed in order. use https://github.com/caolan/async#queue with a concurrency of 1?