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 Sep 3, 2021. It is now read-only.
I need to assert that nodes for a type are unique by a combination of field values.
Since neo4j-graphql-js doesn't allow this at the moment (@uniqueTogether directive ?), I have a cypher script to create the constraint
// Make sure we have unique nodesCREATECONSTRAINTuniqueT10IFNOTEXISTSON (n:T10)
ASSERT (n.date, n.name, n.result, n.m50) ISNODEKEY;
The cypher query works fine, and the constraint shows up in the neo4j desktop
Looking at the doc, I see a dropExisting option. Sure enough, if I set it to false, my constraint is kept. But so are constraints that I might want to see deleted when changing other types in the schema later on.
Could we add a keepWhitelist list of constraints names, so I could do the following ?
Related: #137
Maybe related: #569
I need to assert that nodes for a type are unique by a combination of field values.
Since neo4j-graphql-js doesn't allow this at the moment (@uniqueTogether directive ?), I have a cypher script to create the constraint
The cypher query works fine, and the constraint shows up in the neo4j desktop
But when starting my Apollo server, I get
My type definition:
The related assertSchema call
Looking at the doc, I see a
dropExisting
option. Sure enough, if I set it to false, my constraint is kept. But so are constraints that I might want to see deleted when changing other types in the schema later on.Could we add a
keepWhitelist
list of constraints names, so I could do the following ?The text was updated successfully, but these errors were encountered: