You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great job on the library; it's made my dev life easier. Thanks
However, I have come across an issue that only appears when I am using MongoDB. The issue does not manifest when I switch to traditional relational databases like MySQL.
Specifically, all generated 'XXXIncludeSchema' objects appear as:
Even when the corresponding Prisma.XXXInclude has actual content.
On the other hand, everything works as expected when I am using a traditional relational database like MySQL.
This issue is causing some inconsistencies in my application and I was wondering if this is a known issue or if there's a workaround for it.
Looking forward to your response, and thank you once again for this fantastic library!
@ksdaylight Thanks for reaching out. Since I do not use MongoDB in any of my projects I don't have real usecases. It would be nice if you can provide a schema I can work with.
This could also be something prisma changed in the 5.x.x release since the include schemas were generally empty in my tests I did some month back.
Great job on the library; it's made my dev life easier. Thanks
However, I have come across an issue that only appears when I am using MongoDB. The issue does not manifest when I switch to traditional relational databases like MySQL.
Specifically, all generated 'XXXIncludeSchema' objects appear as:
Even when the corresponding Prisma.XXXInclude has actual content.
On the other hand, everything works as expected when I am using a traditional relational database like MySQL.
This issue is causing some inconsistencies in my application and I was wondering if this is a known issue or if there's a workaround for it.
Looking forward to your response, and thank you once again for this fantastic library!
My environment versions are:
prisma: 5.1.1
zod: 3.21.1
zod-prisma-types: ^2.7.9
The text was updated successfully, but these errors were encountered: