You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm curious as to whether there's a way to wrap ragtime's migrations in a transaction block.
To be clear, I'm not talking about per-migration transactions (i.e., begin - migration - transaction), but rather a cross-migration transaction block:
begin
migration1
migration2
migration3
...
commit
I'm asking because I'm looking at whether I can hastily run all migrations on my test database, execute a test, and then return the state of the world to 0 before doing it all again for each test.
I've been trying to do this in a way that plays nicely with Korma but my guess is that ragtime is handling its own DB connection and so they're not actually sharing the transaction block. Any thoughts on how to handle this?
The text was updated successfully, but these errors were encountered:
I'm curious as to whether there's a way to wrap ragtime's migrations in a transaction block.
To be clear, I'm not talking about per-migration transactions (i.e., begin - migration - transaction), but rather a cross-migration transaction block:
begin
migration1
migration2
migration3
...
commit
I'm asking because I'm looking at whether I can hastily run all migrations on my test database, execute a test, and then return the state of the world to 0 before doing it all again for each test.
I've been trying to do this in a way that plays nicely with Korma but my guess is that ragtime is handling its own DB connection and so they're not actually sharing the transaction block. Any thoughts on how to handle this?
The text was updated successfully, but these errors were encountered: