graphql 2019-11-27 | Slack Archive

@dominicm Can you find me the part of spec where it says so?

The spec is about not mixing and matching queries, mutations, and subscriptions.

queries are allowed to execute in any convienient order.

mutations must execute sequentially; the first mutation must fully complete before the second mutation is executed.

That's fundamentally the only difference between queries and mutations.

And subscriptions are entirely different.

yeah

Wait, can I send two queries in one HTTP request to Lacinia, and I get two answers in one response?

There's nothing stopping you from doing that

lacinia-pedestal might not have that built in but it seems easy enough to check whether the request is an object or an array of objects

query {
  customer(id: 12345) { name }
  order(id: "12345") { date }
}

A single query can hit multiple query operations at the same time.

{"data": {"customer": "fred", "order": "20191128"}}

Yeah, good point. I assumed he was referring to Apollo's query batching but perhaps not

Thanks, yeah I was referring to what people wrote above :) very cool

You could even do multiple similar queries if you use aliases.

2019-11-27