Is there a notion of transaction in GraphQL?

Question

To avoid looking after a ghost, I prefer to check if the notion of a transaction can exist in GraphQL .

Let’s say I have this:

mutation save_changes {
  change01 {
    
  }
  change02 {
    
  }
}

Is there a possibility for change01 to be rolled back if change02 fails?

Only commit the transaction when all operations succeed or roll it back if any of your operation fails. — 1 hour ago

Ken ChanKen Chan 84.1k26 gold badges142 silver badges171 bronze badges · Accepted Answer · 2023-08-21 14:05:40Z

GraphQL is the API technology while transaction is a DB technology. As GraphQL is agnostic to the datasource(s) used to retrieve and persist data , so it is quite normal that GraphQL does not define anything related to the DB transaction and pretty sure it will never to that in the future. It is up to the developer to implement how the transactional behaviour to be.

Is there a notion of transaction in GraphQL?