Are there common patterns for implementing a soft delete with prisma?

Hey @Dali Rojas 👋 I personally would implement a

deletedAt

field in my

schema.prisma

model User {
  id        Int       @default(autoincrement()) @id
  name      String
  deleted   Boolean   @default(false)
  createdAt DateTime  @default(now())
  deletedAt DateTime?
}

And query it via:

await prisma.user.findMany({
    where: {
      deleted: false,
    },
  })

It would also be performant to create an conditional index on your query for non-deleted users as that would be mainly what you would be querying for.

Thank you

@Ryan if I want to use unique key with soft_deleted, add

@@unique([email, deleted, deletedAt], _name_: “uniqueKeys”)

right?

@Leo Hui yes that would be correct

@Ryan it may be wrong, because deletedAt default value is null, null can not judge as unique... so I add another field, deletedId which default value is "", and when it soft deleted, I set deletedId as id (in my case ,id is string)

Yes NULLS cannot be added to

@unique

yes