You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 22, 2023. It is now read-only.
However, in the case where a field is required and a relation, the Create mutation allows you to create an object without the field (because you need to use Add/Merge to create the relation), but if you try and do a Query that includes this field when it's not set an error will be raised.
This can probably be closed if we're happy with the current solution.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have a few cases where we want to model a one-to-many relationship.
Using the neo4j-graphql-js library we haven't found a good way to do this. Currently we use
@relation
to define a many-to-many relationship.@ChristiaanScheermeijer suggested that we could try and use Neo4j constraints. We need to see if this is a suitable solution.
https://github.com/trompamusic/ce-api/pull/90/files/123f1a4849e69dde82543d77dc224d9ac0c8cf2e#r384462860
The text was updated successfully, but these errors were encountered: