I want to delete through custom dql: type Mutation { deleteEntityById(id: String!): Entity @custom(dql: """ upsert { query q($id: string) { E as var(func: type(Entity)) @filter(eq(Entity.id, $id)) { U as Entity.urls M as Entity.medias } …

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 qu…

Why does custom dql not support mutation?

Issues GraphQL

minhaj (Minhaj Shakeel) March 22, 2021, 1:12pm 9

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

Status on Missing Custom Features

Topic		Replies	Views
GraphQL: using results as inputs GraphQL kind:question	2	782	October 19, 2020
Status on Missing Custom Features GraphQL kind:question , dql , custom-directive , custom-resolver	0	658	December 4, 2021
Is it possible to allow certain graphql mutations to only be executed by a lambda? GraphQL kind:question , lambda	4	989	August 8, 2021
Support DQL variables in mutations Dgraph dgraph , kind:enhancement , status:accepted , area:upsert , area:querylang:vars	14	1963	October 4, 2022
Run a dql mutation in slash dgraph lambda Dgraph Cloud mutation , dql , lambda	3	684	March 16, 2021

Why does custom dql not support mutation?

Related Topics