(Reposting to make things clearer) I seem to have run into a bug related to the ‘selectRelationCount’ preview feature. This line causes the below error, but removing the ‘_count: true’ part makes it work. Anyone got any ideas on what is going on?

this.prisma.user.findUnique({where: {id: 1}, include: {_count: true}})

@Nichita Z 👋 Have you added this preview feature to

schema.prisma

and then run

prisma generate

?

Hello, yes indeed! It’s been working OK so far for a while

So an update in the version caused this?

It started crashing after the last deploy. The biggest change I did to the User schema in between was adding an explicit many to many relationship, like this:

pendingFollowers PendingFollowers[] @relation(name: "targets")

pendingFollowing PendingFollowers[] @relation(name: "sources")

So these are both in the user object, and they relate to a model that looks like this:

model PendingFollowers {

source        User     @relation(name: "sources", fields: [sourceId], references: [id])

sourceId      Int

target    User @relation(name: "targets", fields: [targetId], references: [id])

targetId  Int

createdAt   DateTime @default(now())

@@id([sourceId, targetId])

}

I would suggest opening an issue for this here with all the details so that we can look into this.

Okay, will do after a bit more debugging, thx!

Adding a relation shouldn’t normally break the query.

Yeah, apparently it happens if I try to include these counts in the query:

Yes this is a self relation as described here.

You’re right, they’re in the docs, my bad! I’ll try some more stuff and then create the issue