Why does custom dql not support mutation?

[BenW]

@pawan

The initial aim for adding custom DQL was just to give you the ability to perform complex DQL queries like aggregations, multiple var blocks and such. We didn’t support custom DQL mutations for the sake of simplification but we can definitely do that.

Infact, you could right now define a GraphQL query which ultimately does a DQL upsert and that would work. We will be looking into supporting this as well.

+1 for custom DQL mutations.

@minhaj

We are not going to support custom DQL mutations. The best way to achieve this is through lambdas .

Why have you decided not to support custom DQL mutations? Would really appreciate an explanation here. Makes sense to me to have as much of my API, ideally all of it, defined in one place—rather than have backend logic spread across the schema as well as lambda functions.