type Employee {
name: String!
department: Department!
}
type Department {
name: String!
}
I can't model a use case where an employee must belong to a department.
Best answer by Dilini Fernando
View originaltype Employee {
name: String!
department: Department!
}
type Department {
name: String!
}
I can't model a use case where an employee must belong to a department.
Best answer by Dilini Fernando
View originalBeing able to ensure that an employee will always belong to a department is a very common use case in data modeling.
There is no workaround. The reason is the following:
If node X is in space A with a reference to node Y in space B.
If I delete my node Y, but don’t have access to delete your node X, what should happen?
I definitely see the use case, but we will not have a solution for this on the short term.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.