Hey <!here>. I'm looking for people who tried but were not successful with MongoDB for Prisma. Could you share some of the reasons why you couldn't use MongoDB with Prisma? If you're up for it, I'd also love to jump on a quick call to learn more: https://calendly.com/matthewmueller/mongo.

I've tried, was not successful, but that's only because of missing features like embedded documents. So I believe that's not worth wasting your time on a call 😄 Once these missing features will be implemented I believe it would be good enough for my case.

Hey @Matt Mueller (Prisma Client PM), I assume you’re referring to Prisma 2. We tried Prisma 1 and it didn’t work out, but happy to provide insight if you’re curious. We’re trying out Prisma 2 now and running into similar limitations, albeit new ones, but that’s to be expected as it’s still beta.

Hey @Aske, yep Prisma 2. What kinds of new limitations are you running up against?

Hi @Matt Mueller (Prisma Client PM). I am waiting for the official support for mongodb with Keystone which i know is currently held up by this issue, however i did create a small patch to make things run. I was semi successful, however I cant seem to get my relationships to function correctly. Are there any known issues with relationships? I know it is hard to give accurate time frames, but can you give any indication of when that issue will be fixed so that keystone can fully support mongodb? If there is anything i can do to support please let me know as it is currently holding up a project and i am stuck between old versions of keystone not using prisma and my (apparently buggy) patched version of keystone. Thank you!!!!!!

Hey @Matt Mueller (Prisma Client PM), missed your reply here. Sorry about that! With Prisma 2 it’s the lack of native query support, we’ve worked around it but it’s not ideal as it opens additional DB connections.