If I do a mutation in the prisma backend resolver to delete something and I want to delete something else too, how do I make sure both or neither happens (transaction?) Or is that already handled on some other level (on error -> rollback)? (Saw that cascade support will be added later, but how to handle that now?)

you could create a resolver in which you query the data and store in the resolver memory. Then if the deletes fail you could restore the data?

Yeah, but I’m not sure I could restore it all the way