Is this how I should create a hierarchical data structure so Prisma #orm-help

Is this how I should create a hierarchical data st...

Awey

02/06/2021, 10:26 PM

Is this how I should create a hierarchical data structure so I can recursively render my comments?

Copy code

model Comment {
  id        Int       @id @default(autoincrement())
  createdAt DateTime  @default(now()) @map("created_at")
  updatedAt DateTime  @updatedAt @map("updated_at")
  text      String
  author    User?     @relation(fields: [authorId], references: [id])
  authorId  Int?      @map("author_id")
  post      Post?     @relation(fields: [postId], references: [id])
  postId    Int?      @map("post_id")
  replies   Comment[] @relation("CommentToComment")
  parent    Comment?  @relation("CommentToComment", fields: [parentId], references: [id])
  parentId  Int?      @map("parent_id")

  @@map("comments")
}

✅ 1

Awey

02/06/2021, 10:26 PM

I'm hoping something like this would be possible on the front end.

https://i.postimg.cc/V6st1vkv/Screen-Shot-2021-01-19-at-1-43-55-AM.png▾

nikolasburk

02/08/2021, 2:45 PM

Hey Adam 👋 yes, this looks good to me! You probably already saw this, but these kinds of self-referential relationships are also documented here 🙂

👍 1

Awey

02/09/2021, 5:19 AM

Yes I did read that. I just was not confident. This is what is considered an adjacency list right?

Awey

02/13/2021, 12:51 AM

@nikolasburk I would have to make a mutation for createComment and createReply right? I'm asking because I tried to use createComment for both and sometimes you don't have a parentId to pass as an argument because it's a top level comment and other times you do because it's a reply. But in the createComment mutation there is no way to set that behaviour. I kept ending up with an authorization error when I did something like this.

Copy code

...
parentId: {
  connect: {
    id: args.parentId ? args.parentId : null
  }
}
...

Open in Slack

Previous Next