Hi. Does GraphQL kotlin preserve order of certain functions send in one graphql request? I have something like this:

mutation {
  deleteObj1(where){
    affectedRows
  }

  deleteObj2(where){
    affectedRows
  }

  deleteObj3(where){
    affectedRows
  }

  deleteObj4(where){
    affectedRows
  }
}

If order of executed functions will change, there can be thrown foreign key constraint condition -> I need to execute mutations like DELETE CASCADE...

The actual graphql executor comes from graphql-Java, and I’m sure it’s spec-compliant and runs mutations in sequence, top to bottom. But if you need transactionality, you should really wrap these up in a single mutation

if you use

graphql-kotlin-spring-server

then by default yes they will execute sequentially, that being said - as was pointed above I’d highly recommend to refactor your schema to expose single mutation that handles all of that

Treat each mutation independently. Just like with resolvers, how you execute (serially, sequentially) is implementation detail.