Do per-migration transactions (instead of one transaction for all needed migrations)

[tamstrup]

I have run into an issue where I add an additional value to an enum, but I cannot use that value in subsequent migrations because all needed migrations run in a single transaction.

Would there be any problem in making a transaction per migration instead?