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…

I suspect that allowing mutations via @custom would cause a lot of headaches - your graphql code will no longer be deterministic. But I think @pawan might be the best person to answer this and perhaps offer some discussions around it.

The dql has many features that the GraphQL API cannot do. If custom dql does not support mutation, it will bring a lot of difficulties and even have to give up the GraphQL API.

Can you please explain your use case, may be there is some other way to achieve that?

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

@minhaj Could you guys add JSON Mutation Format support to lambdas? [image] Slash DGraph Lambdas Feature Requests / Small Change This is probably the easiest fix. Allow DQL within lambdas to accept JSON Mutation Format. You could easily update the code here . My suggestion would be something as …

[image] jdgamble555: Could you guys add JSON Mutation Format support to lambdas? Yes, we will get this done for the 21.03 release.

Hi, I also have a similar use case. I find it very strange and not very homogeneous to have this option for queries and not for mutations. Are you planning to add this option in the future? Regards!

[image] 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 …

Why does custom dql not support mutation?

Issues GraphQL

abhimanyusinghgaur (Abhimanyu Singh Gaur) March 23, 2021, 6:55am 11

Yes, we will get this done for the 21.03 release.

Recommended way of running queries or mutations from the backend?

Topic		Replies	Views
Status on Missing Custom Features GraphQL kind:question , dql , custom-directive , custom-resolver	0	724	December 4, 2021
Run a dql mutation in slash dgraph lambda Dgraph Cloud mutation , dql , lambda	3	788	March 16, 2021
Improvements to Custom DQL feature GraphQL area:graphql	0	817	January 28, 2021
How to convert GraphQL mutation to dql Dgraph Cloud graphql , kind:question , dql	9	1948	March 18, 2021
How to implement `custom resolvers` in DQL? Dgraph kind:question	3	582	December 1, 2021

Why does custom dql not support mutation?

Related topics