Kit Isaev
01/14/2019, 3:01 PMtype User {
id: ID! @unique
sessions: [Session!]! @relation(name: "UserToSessions", onDelete: CASCADE)
...
}
type Session {
id: ID! @unique
user: User! @relation(name: "UserToSessions")
...
}
Why is "sessions" field on type "user" nullable in the resulting Prisma API?
type User {
sessions(...): [Session!]
}
I've checked multiple cases, this effect always persists in one-to-many relations. The one-to-many relation field is always nullable, regardless of whether it is marked as nullable or non-nullable in the datamodel. Thanks in advance!