# GraphQL **URL:** https://discuss.dgraph.io/c/issues/graphql/39.md [Latest](https://discuss.dgraph.io/latest.md) · [Categories](https://discuss.dgraph.io/categories.md) · [Tags](https://discuss.dgraph.io/tags.md) --- ## [About the GraphQL category](https://discuss.dgraph.io/t/about-the-graphql-category/8336)
**Author:** [@mrjn](https://discuss.dgraph.io/u/mrjn)\ **Replies:** 0
(Replace this first paragraph with a brief description of your new category. This guidance will appear in the category selection area, so try to keep it below 200 characters.) Use the following paragraphs for a longer d… --- ## [Order by enum type](https://discuss.dgraph.io/t/order-by-enum-type/14292)
**Author:** [@jdgamble555](https://discuss.dgraph.io/u/jdgamble555)\ **Replies:** 2\ **Last updated:** [February 5, 2025, 6:16am UTC](https://discuss.dgraph.io/t/order-by-enum-type/14292 "2025-02-05T06:16:59Z")
I am having a problem ordering by an enum type: enum Direction { forward backward } type Garage { id name cars: \[Car\] ... } type Car { id: ID! direction: Direction! @search ... } And my query: query… --- ## [Cascade Directive with Pagination produces unexpected results](https://discuss.dgraph.io/t/cascade-directive-with-pagination-produces-unexpected-results/8862)
**Author:** [@diggy](https://discuss.dgraph.io/u/diggy)\ **Replies:** 14\ **Last updated:** [January 1, 2025, 6:27pm UTC](https://discuss.dgraph.io/t/cascade-directive-with-pagination-produces-unexpected-results/8862 "2025-01-01T18:27:26Z")
Moved from GitHub dgraph/5930 Posted by amaster507: What version of Dgraph are you using? docker image dgraph :master v2.0.0-rc1-448-gd5892dc0c Have you tried reproducing the issue with the latest release? N/A as @c… --- ## [Editable @id fields](https://discuss.dgraph.io/t/editable-id-fields/13295)
**Author:** [@JatinDevDG](https://discuss.dgraph.io/u/JatinDevDG)\ **Replies:** 4\ **Last updated:** [January 1, 2025, 5:42am UTC](https://discuss.dgraph.io/t/editable-id-fields/13295 "2025-01-01T05:42:08Z")
thanks @JatinDevDG Is it correct that the fields will be not editable when they are made @id fields ? I wanted the behavior of unique but still editable. For now I am just going to check for this before adding into DB… --- ## [Can interfaces implement other interfaces in GraphQL?](https://discuss.dgraph.io/t/can-interfaces-implement-other-interfaces-in-graphql/10013)
**Author:** [@gorillastanley](https://discuss.dgraph.io/u/gorillastanley)\ **Replies:** 7\ **Last updated:** [December 5, 2024, 10:45pm UTC](https://discuss.dgraph.io/t/can-interfaces-implement-other-interfaces-in-graphql/10013 "2024-12-05T22:45:16Z")
Eg interface A { name: String } interface B implements A { id: String! @id } --- ## [\`@default\` was merged yet I get \`undefined directive default.\`](https://discuss.dgraph.io/t/default-was-merged-yet-i-get-undefined-directive-default/19526)
**Author:** [@adriangalilea](https://discuss.dgraph.io/u/adriangalilea)\ **Replies:** 1\ **Last updated:** [August 23, 2024, 9:42am UTC](https://discuss.dgraph.io/t/default-was-merged-yet-i-get-undefined-directive-default/19526 "2024-08-23T09:42:55Z")
Apparently @default was added here But I can’t use it, there’s also this issue tracking it, so it’s hard to tell what’s going on, there’s no reference to @default on the docs either… Can someone shed some light? --- ## [DQL querying with an array of parameters](https://discuss.dgraph.io/t/dql-querying-with-an-array-of-parameters/19519)
**Author:** [@adriangalilea](https://discuss.dgraph.io/u/adriangalilea)\ **Replies:** 3\ **Last updated:** [August 19, 2024, 6:23pm UTC](https://discuss.dgraph.io/t/dql-querying-with-an-array-of-parameters/19519 "2024-08-19T18:23:35Z")
The documentation states: Query parameterization Parameters must have a name starting with a \` symbol. must have a type int, float, bool or string. may have a default value. In the example below, $age has a default v… --- ## [Order desc returning no results with cascade and first](https://discuss.dgraph.io/t/order-desc-returning-no-results-with-cascade-and-first/16739)
**Author:** [@danielhr](https://discuss.dgraph.io/u/danielhr)\ **Replies:** 6\ **Last updated:** [June 20, 2024, 10:33am UTC](https://discuss.dgraph.io/t/order-desc-returning-no-results-with-cascade-and-first/16739 "2024-06-20T10:33:54Z")
\[ X\] SlashGraphQL v21.03.0-78-ge4ad0b113 I’m running a query that’s using a parametrized cascade ordering and should return the first 25 results. The query works as expected when using descending order for items but re… --- ## [Directive idea to support var blocks in GraphQL](https://discuss.dgraph.io/t/directive-idea-to-support-var-blocks-in-graphql/14419)
**Author:** [@amaster507](https://discuss.dgraph.io/u/amaster507)\ **Replies:** 7\ **Last updated:** [June 5, 2024, 5:48pm UTC](https://discuss.dgraph.io/t/directive-idea-to-support-var-blocks-in-graphql/14419 "2024-06-05T17:48:09Z")
Idea comes from a recent blog post that gave several shoutouts to Dgraph :sunglasses: which references: What I found interesting was a directive called @export which is used to export variables to be used in later … --- ## [Bundle mutations and rollback in case of error](https://discuss.dgraph.io/t/bundle-mutations-and-rollback-in-case-of-error/13690)
**Author:** [@maaft](https://discuss.dgraph.io/u/maaft)\ **Replies:** 5\ **Last updated:** [March 17, 2024, 4:22pm UTC](https://discuss.dgraph.io/t/bundle-mutations-and-rollback-in-case-of-error/13690 "2024-03-17T16:22:15Z")
When adding data in complex schemas, often you have side-effects that have to be accounted for. This means that one mutation is often followed by several others. If one of these mutations fail, currently the client has … --- ## [FTL failed to login error="rpc error: code = Unknown desc = unauthorized ip address: 192.168.1.103"](https://discuss.dgraph.io/t/ftl-failed-to-login-error-rpc-error-code-unknown-desc-unauthorized-ip-address-192-168-1-103/19196)
**Author:** [@shufilk](https://discuss.dgraph.io/u/shufilk)\ **Replies:** 0\ **Last updated:** [February 19, 2024, 2:25pm UTC](https://discuss.dgraph.io/t/ftl-failed-to-login-error-rpc-error-code-unknown-desc-unauthorized-ip-address-192-168-1-103/19196 "2024-02-19T14:25:52Z")
Report a GraphQL Bug What edition and version of Dgraph are you using? Edition: Dgraph Cloud (GraphQL feature) Dgraph On-Prem (EE) Dgraph (community edition) If you are using the community edition or enterprise … --- ## [Null empty node](https://discuss.dgraph.io/t/null-empty-node/19002)
**Author:** [@Sanjaer](https://discuss.dgraph.io/u/Sanjaer)\ **Replies:** 0\ **Last updated:** [October 19, 2023, 2:04pm UTC](https://discuss.dgraph.io/t/null-empty-node/19002 "2023-10-19T14:04:00Z")
Dgraph version : v23.0.0 Dgraph codename : dgraph Dgraph SHA-256 : aafa0fe5a65059eec94703e2ed6d5c88a80317e9ee7e8c3776a6abf60ae78fc4 Commit SHA-1 : 38980bc Commit timestamp : 2023-05-08 14:56:12 -0700 Branch… --- ## [Export data from Dgraph error: "resolving export failed because task failed"](https://discuss.dgraph.io/t/export-data-from-dgraph-error-resolving-export-failed-because-task-failed/18999)
**Author:** [@rebamundo](https://discuss.dgraph.io/u/rebamundo)\ **Replies:** 0\ **Last updated:** [October 18, 2023, 8:59pm UTC](https://discuss.dgraph.io/t/export-data-from-dgraph-error-resolving-export-failed-because-task-failed/18999 "2023-10-18T20:59:24Z")
Edition: Dgraph (community edition) ▶ Dgraph Version Have you tried reproducing the issue with the latest release? No Steps to reproduce the issue $ sudo docker exec dgraph\_alpha1.1.0qabj152a1fz8oyqu7u2srx0l curl htt… --- ## [TypeORM Entity Association Returns Null for Related Fields in GraphQL Nexus Schema](https://discuss.dgraph.io/t/typeorm-entity-association-returns-null-for-related-fields-in-graphql-nexus-schema/18861)
**Author:** [@xAdvitya](https://discuss.dgraph.io/u/xAdvitya)\ **Replies:** 0\ **Last updated:** [August 22, 2023, 12:01am UTC](https://discuss.dgraph.io/t/typeorm-entity-association-returns-null-for-related-fields-in-graphql-nexus-schema/18861 "2023-08-22T00:01:35Z")
I’m currently building a GraphQL API using TypeORM and Nexus Schema. I’ve defined several entities with associations between them, such as Product, Brand, and User. The problem I’m facing is that when I query the Product… --- ## [How To Use Nullable @id Fields?](https://discuss.dgraph.io/t/how-to-use-nullable-id-fields/18834)
**Author:** [@zaneaw](https://discuss.dgraph.io/u/zaneaw)\ **Replies:** 2\ **Last updated:** [August 15, 2023, 10:40pm UTC](https://discuss.dgraph.io/t/how-to-use-nullable-id-fields/18834 "2023-08-15T22:40:10Z")
Report a GraphQL Bug What edition and version of Dgraph are you using? Edition: SlashGraphQL Dgraph (community edition/Dgraph Cloud) If you are using the community edition or enterprise edition of Dgraph, please lis… --- ## [Value variable causes "eq expects atleast 1 argument"](https://discuss.dgraph.io/t/value-variable-causes-eq-expects-atleast-1-argument/18813)
**Author:** [@jantoine](https://discuss.dgraph.io/u/jantoine)\ **Replies:** 6\ **Last updated:** [July 30, 2023, 8:40am UTC](https://discuss.dgraph.io/t/value-variable-causes-eq-expects-atleast-1-argument/18813 "2023-07-30T08:40:47Z")
NOTE: I’m using the GraphQL issue tag because I couldn’t find a DQL one Report a DGraph Bug What edition and version of Dgraph are you using? Edition: SlashGraphQL Dgraph (community edition/Dgraph Cloud) If you are… --- ## [Edges are not being generated](https://discuss.dgraph.io/t/edges-are-not-being-generated/18723)
**Author:** [@GandiYaswanthSai](https://discuss.dgraph.io/u/GandiYaswanthSai)\ **Replies:** 1\ **Last updated:** [June 19, 2023, 5:35pm UTC](https://discuss.dgraph.io/t/edges-are-not-being-generated/18723 "2023-06-19T17:35:31Z")
Report a GraphQL Bug I have a scenario where I need to update the existing schema(containing 2 types Type1 & Type2) with relationships/edges after few 100’s of records are already been inserted into those respective ty… --- ## [I cannot remove references in a data array that no longer exist](https://discuss.dgraph.io/t/i-cannot-remove-references-in-a-data-array-that-no-longer-exist/18702)
**Author:** [@MaritoRT](https://discuss.dgraph.io/u/MaritoRT)\ **Replies:** 1\ **Last updated:** [June 9, 2023, 3:58am UTC](https://discuss.dgraph.io/t/i-cannot-remove-references-in-a-data-array-that-no-longer-exist/18702 "2023-06-09T03:58:14Z")
Delete data from a “type” FieldRule, and in another “type” Product there was an array of fieldrules \[FieldRule\], when I do a product query, the reference to the ids of this FieldRule still appears, but in FieldRule they … --- ## [Can we have support for file-uploads and downloads?](https://discuss.dgraph.io/t/can-we-have-support-for-file-uploads-and-downloads/12731)
**Author:** [@maaft](https://discuss.dgraph.io/u/maaft)\ **Replies:** 10\ **Last updated:** [March 9, 2023, 12:36pm UTC](https://discuss.dgraph.io/t/can-we-have-support-for-file-uploads-and-downloads/12731 "2023-03-09T12:36:14Z")
Continuing the discussion from: http://dgraph.discourse.group/t/can-we-have-remote-scalars/11726/10 When building applications that use databases, often binary data has to be stored somewhere. This is often done by storing … --- ## [Alpha does not communicate with lambda when using \`@lambdaOnMutate\`](https://discuss.dgraph.io/t/alpha-does-not-communicate-with-lambda-when-using-lambdaonmutate/18248)
**Author:** [@subrat\_gupta](https://discuss.dgraph.io/u/subrat_gupta)\ **Replies:** 3\ **Last updated:** [February 7, 2023, 9:42pm UTC](https://discuss.dgraph.io/t/alpha-does-not-communicate-with-lambda-when-using-lambdaonmutate/18248 "2023-02-07T21:42:34Z")
Report a GraphQL Bug alpha does not communicate with lambda when using @lambdaOnMutate Expected behaviour and actual result. when running any delete, add, update query on any type with @lambdaOnMutate(add: true, upda… --- ## [Fulltext search across multiple fields](https://discuss.dgraph.io/t/fulltext-search-across-multiple-fields/14354)
**Author:** [@amaster507](https://discuss.dgraph.io/u/amaster507)\ **Replies:** 7\ **Last updated:** [January 11, 2023, 2:51pm UTC](https://discuss.dgraph.io/t/fulltext-search-across-multiple-fields/14354 "2023-01-11T14:51:09Z")
Experience Report for Feature Request What you wanted to do Fulltext search across multiple fileds What you actually did Nothing, yet, as it is not possible. Why that wasn’t great, with examples Alternatively we are co… --- ## [\[Bug\] StringHashFilter of update mutation does not work correctly](https://discuss.dgraph.io/t/bug-stringhashfilter-of-update-mutation-does-not-work-correctly/12184)
**Author:** [@maaft](https://discuss.dgraph.io/u/maaft)\ **Replies:** 2\ **Last updated:** [January 6, 2023, 6:39pm UTC](https://discuss.dgraph.io/t/bug-stringhashfilter-of-update-mutation-does-not-work-correctly/12184 "2023-01-06T18:39:39Z")
The StringHashFilter of update mutations has unexpected behaviour when eq is set to a value and in is set to null: schema: type Foo { id: String! @id value: Int! } Add two (or more) foos: mutation { addFoo(input:… --- ## [Allow overriding the JWKURL expireTime in GraphQL Authorization schema](https://discuss.dgraph.io/t/allow-overriding-the-jwkurl-expiretime-in-graphql-authorization-schema/18154)
**Author:** [@mattboardman](https://discuss.dgraph.io/u/mattboardman)\ **Replies:** 0\ **Last updated:** [January 5, 2023, 8:28pm UTC](https://discuss.dgraph.io/t/allow-overriding-the-jwkurl-expiretime-in-graphql-authorization-schema/18154 "2023-01-05T20:28:38Z")
Report a GraphQL Bug The JWKURL refresh is driven by a response header: Cache-Control: max-age=$SOME\_VALUE code pointer - dgraph/graphql/authorization/auth.go at c04ce807f9399cc9d00159d54333d7a6a1de18fe · dgraph-io/dgr… --- ## ["unknown type" issue after dropping Dgraph schema/data and then resetting the schema](https://discuss.dgraph.io/t/unknown-type-issue-after-dropping-dgraph-schema-data-and-then-resetting-the-schema/18108)
**Author:** [@Tyler\_D](https://discuss.dgraph.io/u/Tyler_D)\ **Replies:** 4\ **Last updated:** [December 29, 2022, 7:18pm UTC](https://discuss.dgraph.io/t/unknown-type-issue-after-dropping-dgraph-schema-data-and-then-resetting-the-schema/18108 "2022-12-29T19:18:27Z")
Report a GraphQL Bug I am having an issue and wondering if anyone here has any insight into it. I am loading a fairly large schema into dgraph (just running locally using the Dgraph docker image) and for some reason, a l… --- ## [Dgraph query failed because Dgraph execution failed because Some variables are declared multiple times](https://discuss.dgraph.io/t/dgraph-query-failed-because-dgraph-execution-failed-because-some-variables-are-declared-multiple-times/18072)
**Author:** [@droslean](https://discuss.dgraph.io/u/droslean)\ **Replies:** 11\ **Last updated:** [December 9, 2022, 12:43am UTC](https://discuss.dgraph.io/t/dgraph-query-failed-because-dgraph-execution-failed-because-some-variables-are-declared-multiple-times/18072 "2022-12-09T00:43:19Z")
This error message is useless. Is there any way to figure out why my query is wrong? --- ## [Update mutation removing connection between nodes in one field and setting the connection on a different field fails](https://discuss.dgraph.io/t/update-mutation-removing-connection-between-nodes-in-one-field-and-setting-the-connection-on-a-different-field-fails/15729)
**Author:** [@jackl](https://discuss.dgraph.io/u/jackl)\ **Replies:** 9\ **Last updated:** [November 30, 2022, 7:31pm UTC](https://discuss.dgraph.io/t/update-mutation-removing-connection-between-nodes-in-one-field-and-setting-the-connection-on-a-different-field-fails/15729 "2022-11-30T19:31:50Z")
Report a GraphQL Bug What edition and version of Dgraph are you using? Edition: SlashGraphQL Dgraph (community edition/Dgraph Cloud) If you are using the community edition or enterprise edition of Dgraph, please … --- ## [Lambda return errors](https://discuss.dgraph.io/t/lambda-return-errors/13994)
**Author:** [@Anibal\_Aguirre](https://discuss.dgraph.io/u/Anibal_Aguirre)\ **Replies:** 4\ **Last updated:** [November 8, 2022, 10:12am UTC](https://discuss.dgraph.io/t/lambda-return-errors/13994 "2022-11-08T10:12:07Z")
Hi, We are testing lambdas mutation resolvers to add some business logic. We would need to return some validation errors from the lambdas mutation resolver. I’ve been playing adding error object to the errors JSON arr… --- ## [Directive Default Doesn't work](https://discuss.dgraph.io/t/directive-default-doesnt-work/17904)
**Author:** [@AdrianMolero94](https://discuss.dgraph.io/u/AdrianMolero94)\ **Replies:** 3\ **Last updated:** [October 26, 2022, 7:22pm UTC](https://discuss.dgraph.io/t/directive-default-doesnt-work/17904 "2022-10-26T19:22:28Z")
Report a Dgraph Bug - the default directive does not currently work What version of Dgraph are you using? - Latest in previous versions you could place the default value inside the schema, however in the version released… --- ## [Interfaces are not GraphQL compliant](https://discuss.dgraph.io/t/interfaces-are-not-graphql-compliant/9725)
**Author:** [@ajeet](https://discuss.dgraph.io/u/ajeet)\ **Replies:** 12\ **Last updated:** [December 8, 2020, 6:19am UTC](https://discuss.dgraph.io/t/interfaces-are-not-graphql-compliant/9725 "2020-12-08T06:19:44Z")
This is how the GraphQL spec defines interfaces: interface NamedEntity { name: String } type Person implements NamedEntity { name: String age: Int } Notice how the name field is repeated in the type implementing… --- ## [Mutation failed because Dgraph execution failed because : context deadline exceeded](https://discuss.dgraph.io/t/mutation-failed-because-dgraph-execution-failed-because-context-deadline-exceeded/15221)
**Author:** [@amaster507](https://discuss.dgraph.io/u/amaster507)\ **Replies:** 10\ **Last updated:** [September 21, 2022, 2:38am UTC](https://discuss.dgraph.io/t/mutation-failed-because-dgraph-execution-failed-because-context-deadline-exceeded/15221 "2022-09-21T02:38:59Z")
Report a GraphQL Bug What edition and version of Dgraph are you using? Edition: SlashGraphQL Dgraph (community edition/Dgraph Cloud) If you are using the community edition or enterprise edition of Dgraph, please li… [Next page](https://discuss.dgraph.io/c/issues/graphql/39.md?page=1)