I’m using Prisma in a Next.js app, and I want to ensure that the Prisma client is only instantiated on the server-side and never exposed to the client. However, I’m concerned that in my current setup, I might be accidentally exposing the prisma variable to the client.

I’m facing the issue that my webcrawler doesn’t put the data in the right structure to put it into my database. I don’t see the difference between the object I provide to specialFeatures and the object prisma wants.

I’m facing the issue that my webcrawler doesn’t put the data in the right structure to put it into my database. I don’t see the difference between the object I provide to specialFeatures and the object prisma wants.

I’m facing the issue that my webcrawler doesn’t put the data in the right structure to put it into my database. I don’t see the difference between the object I provide to specialFeatures and the object prisma wants.

I’m facing the issue that my webcrawler doesn’t put the data in the right structure to put it into my database. I don’t see the difference between the object I provide to specialFeatures and the object prisma wants.

My server component refresh only after first submit

so I created a calendar wherein I need to show the current data in that day, like a filter function, but the problem I’m encountering right now, is I don’t know how can I pass the data from client side to server side in NextJS. What I’m trying to achieve is when the client press a certain day, it will pass to the backend.

I’m trying to use a more generic method to get data from prisma, and my function currently looks like this:

In Prisma, I know we can filter with where the records that we include in a certain .findMany request as specified in the doc: