Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[FEATURE]: GraphQL @id uniqueness at interface level #8434

Closed
rderbier opened this issue Nov 16, 2022 · 3 comments
Closed

[FEATURE]: GraphQL @id uniqueness at interface level #8434

rderbier opened this issue Nov 16, 2022 · 3 comments
Labels
area/graphql Issues related to GraphQL support on Dgraph. dgraph Issue or PR created by an internal Dgraph contributor. kind/feature Something completely new we should consider. v21.12 supposedly corrected in v21.12

Comments

@rderbier
Copy link
Contributor

Have you tried Dgraph before this proposal? and did not find anything similar?

No response

What you wanted to do.

In v22.0, @id fields in the interface are unique only in one implementing type.
But there are several use cases that require @id field to be unique across all the implementation types.
Also currently. get a query on the interface can result in unexpected errors as we can have multiple implementing types have the same value for that @id field.

PR merged in v21.13 to be picked in v22.x.y

See details at #7710

What you actually did.

No response

Why wasn't it great, with examples.

No response

Additional information.

No response
@rderbier rderbier added the kind/feature Something completely new we should consider. label Nov 16, 2022
@skrdgraph
Copy link
Contributor

PR merged in v21.13 to be picked in v22.x.y

guessing you mean 22.12?

@rderbier rderbier added area/graphql Issues related to GraphQL support on Dgraph. v21.12 supposedly corrected in v21.12 labels Nov 28, 2022
@MichelDiz MichelDiz added the dgraph Issue or PR created by an internal Dgraph contributor. label Mar 7, 2023
@xnoreq
Copy link

xnoreq commented May 3, 2023

Having the same issue. This is blocking us from upgrading from v21 to v22.

@mangalaman93
Copy link
Contributor

Fixed in #8876

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/graphql Issues related to GraphQL support on Dgraph. dgraph Issue or PR created by an internal Dgraph contributor. kind/feature Something completely new we should consider. v21.12 supposedly corrected in v21.12
Milestone
No milestone
Development

No branches or pull requests
5 participants
@mangalaman93 @xnoreq @MichelDiz @rderbier @skrdgraph