Starting a database transaction in a mutation contesxt

[francipvb]

Hello all,

I am trying to ensure all mutations run inside a single database transaction.

I realyzed I need these things:

• A way to detect if the running query is a mutation, query or subscription.
• A way to run code before the the actual query resolvers.
• A way to run code after the actual query resolver(s).

I am using the FastAPI integration to leverage dependency injection, but I don't have a way to run some code before the query is executed and then another code chunk after the query execution ends, successfully or not.

The motivation for this is that I am developing a mutation system that adds modifying resolvers inside resolved mutation results got from root.

[DoctorJohn]

Hi, did you already take a look at the Strawberry extensions system?

You could possibly make use of the on_operation or on_execute lifecycle hooks to run code before and after execution of your resolvers. Via self.execution_context you should be able to figure out whether your operation is a query, mutation or subscription.

[francipvb]

Hello,

Yes, this is what I did.