Harshit Pant

I will classify this as a bug in schema resolution as schema is correctly stored inside a `prisma` folder. We can also explore if we need to expose a env...

I am marking this as a new feature request. Currently nested createMany many is not implemented.

I can confirm this. For now you can workaround it by adding a manual postinstall script to your package running `prisma generate` like so: ```json { "name": "app", "version": "1.0.0",...

Right now we are not polyfilling any database features. Actually in Prisma 1 and in the very early versions of Prisma 2 we also used to create an enum table...

Another report: https://github.com/prisma/prisma/issues/5743 I added the candidate label to this.

I wasn't able to reproduce this. Just to make sure I understood this correctly, you generated the migrations on a MySQL 8 servers and when you are trying to apply...

Related: https://github.com/prisma/specs/issues/382

@tlonist-sang Please see https://github.com/prisma/specs/issues/330 and https://github.com/prisma/specs/issues/382. For now we have decided to not to polyfill database features. More details about the decision has been mentioned in the above issues. This...

I can reproduce the problem with 3.12 but with 4.10 we throw the following error when generating the client: But the original problem is still reproducible even after fixing the...

Doesn't upsert solve this for you: https://www.prisma.io/docs/reference/api-reference/prisma-client-reference#upsert Upsert basically will insert if `where` condition is not met, otherwise it will update the record which sounds like what you are describing.