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
Hi, I'm using SQLAlchemyInitPlugin in my app but struggle to implement a "rollback recipe" like this one for SQLAlchemy.
Is there an example somewhere on how to do this or does someone have some tips?
From what I understand: to implement the recipe a connection must be started before the specific app test runs so that the next database session injected can be bound to that connection. After validating the return statement the transaction can be rolled back to the save point. However, since the plugin is quite complex/nested to an outsider I find it difficult to identify the spot where I'd have to insert an override. And I'm not sure if it's so difficult because I'm overlooking something or because it's just not possible.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I'm using
SQLAlchemyInitPlugin
in my app but struggle to implement a "rollback recipe" like this one for SQLAlchemy.Is there an example somewhere on how to do this or does someone have some tips?
From what I understand: to implement the recipe a connection must be started before the specific app test runs so that the next database session injected can be bound to that connection. After validating the return statement the transaction can be rolled back to the save point. However, since the plugin is quite complex/nested to an outsider I find it difficult to identify the spot where I'd have to insert an override. And I'm not sure if it's so difficult because I'm overlooking something or because it's just not possible.
Beta Was this translation helpful? Give feedback.
All reactions