So the Password table is a relation to the User. but why is this modelled in a seperate table?

Hello @Jordansz 👋 It isn’t necessary to model Password in a separate table, As only the hash is stored in the Password model and there is a 1:1 relation between both models, you could instead keep the hash field in the User model as well.

model User {
  id    String @id @default(cuid())
  email String @unique

  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt

  hash     String
  notes    Note[]
}

👋 Hello @Jordansz have you perhaps have a chance to check Nurul's answer? Let us know if you still have questions!