Preview feature feedback: referentialIntegrity

[tomhoule]

Please share your feedback about the referentialIntegrity preview feature released in v3.1.1 in this issue.

• If you encounter a bug, please open a bug report in this repo.
• If the feature is working well for you, please share this in a comment below or leave a 👍 on this issue.

If you have any questions, don't hesitate to ask them in the #product-feedback channel in the Prisma Slack.

[SynergyEvolved]

Hi there,
I am curious as to why there is no mention of Vitess which is a CNCF graduated project, instead Prisma only mentions the commercial version of it Planetscale. https://www.prisma.io/docs/reference/database-reference/supported-databases#preview

[janpio]

Because no one ever asked to use Prisma with Vitess @SynergyEvolved, but many people asked for PlanetScale support (which is a specially configured deployment of Vitess with specific settings activated). We are partially testing on Vitess, but only with configuration that makes it PlanetScale like as well.

Please open an issue for explicit Vitess support and we can look into doing the work to confirm this fully working as well.

[niwatoliver]

I am using planetscale and the following error occurs when the number of data is large.

PrismaClientUnknownRequestError: 
Invalid `prisma.room.findMany()` invocation:


Error occurred during query execution:
ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(Server(ServerError { code: 1153, message: "rpc error: code = ResourceExhausted desc = grpc: received message larger than max (24831606 vs. 16777216)", state: "42000" })) })

I assume that this is probably caused by the use of IN clauses in the part of the query that should be issued with a JOIN.

await prisma.room.findMany({
        where: { status: NextAction.COMPLETE },
        include: { matches: true },
});

Currently I am using take and skip to work around this, but it would be great if you could fix this as a bug.

[Jolg42]

Hi @minakawa-daiki Could you create an issue here?
If you could provide reproduction steps it would help a lot.

Note: This is maybe unrelated to the referentialIntegrity feature

[niwatoliver]

OK.
Please give me some time as I need a large amount of data to reproduce it.

[Jolg42]

@minakawa-daiki did you get a chance to reproduce it?

[niwatoliver]

@Jolg42 Sorry. I have not taken the time to verify it by avoiding it in other ways.

[Jolg42]

@pfried I will mark these comments off topic for this issue, I created a separate issue based on your message here:
#16439

[janpio]

Thanks everyone for your feedback, Relation Mode (with preview feature referentialIntegrity went Generally Available with 4.7.0. Read more about it in the documentation: https://www.prisma.io/docs/concepts/components/prisma-schema/relations/relation-mode