protecinnovations/dbmarshal — Issue #7: Updates happen in the wrong order
Author: jezhalford
Created: 2012-03-05 11:39:06+00:00
State: open

At the moment, things happen like this -

1. Drop triggers and sprocs
2. Re-add triggers and sprocs
3. Run revisions.

This is no good because because the tables that a trigger or sproc rely on might be created by a revision. The fix is to do this -

1. Drop triggers and sprocs
2. Run revisions.
3. Re-add triggers and sprocs