GraphQl One-Direction Relationship

Question

I'd like my user to have a list of workouts (they can be active, completed, todo). Do I have to make a link from Workout to user in order to make this work? Is there no other way? Having a link back seems weird because I'd have a loop user>workout>user>workout...

I'm not sure if this is supposed to be done in graphql, I'm new to graphql. I currently have the following schema:

type User {
    email: String @unique
    fullName: String
    birthDate: Date
    weight: Int
    height: Int
    country: String
    trainingFrequency: Int
    trainingGoal: String
    isOnboarded: Boolean
    workouts: [Workout]
}

type Workout {
    name: String!
    state: State!
}

enum State {
  ACTIVE
  TODO
  COMPLETED
}

type Query {
    allUsers: [User!]!
    findUserByEmail(email: String!): User
}

One direction and two directions relationship between two Object types, both of them are ok. See https://stackoverflow.com/questions/53863934/is-graphql-schema-circular-reference-an-anti-pattern — Lin Du, Sep 10 '21 at 11:47

score 1 · Accepted Answer · answered Sep 14 '21 at 20:18

With Fauna, a two way relationship is always created for you when you use the @relation directive. In a one-to-many relationship a reference will be stored in all of the many-side Documents (Workout type in your case). Traversing the graph from the one-side (User type) to the many-side is made possible with an Index that is automatically generated for you.

Yes, you can query (nearly) infinitely cyclically, but in practice, there is no benefit to it.

Make sure you include the @relation directive.

type User {
    email: String @unique
    fullName: String
    birthDate: Date
    weight: Int
    height: Int
    country: String
    trainingFrequency: Int
    trainingGoal: String
    isOnboarded: Boolean
    workouts: [Workout] @relation
}

type Workout {
    name: String!
    state: State!
    owner: User! @relation
}

GraphQl One-Direction Relationship

1 Answers1