Fork me on GitHub

How are folks using relational DBs handling transactions in lacinia. Is it possible to define transactional semantics for multiple mutations in a query? Where would we hook into that in the lacinia api? Or is it better to define the transactional boundary at a single mutation?


By the GraphQL spec, it kind of needs to be a single mutation. Since when there are several mutations they need to be done in order, and kind of wait for each one to be completed before executing the next one.


Yes, you need to think in terms of mapping the schema against your use-cases, rather than your data.