Find a better way to manage/order migrations #53
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It's a pain every time you want to add a migration in the middle of the list.
I'm also playing with the idea of adding some preprocessor logic, so we can generate
INSERT/UPDATE/DELETEtriggers with similar effect statements. Is it worth the added overhead and reduction in replayability?