Regarding prisma 3.14 and MongoDB: I'm trying to get embedded documents working with mongodb, using prisma 3.14 and the structure according to the schema provided in the release notes of prisma 3.10 ( https://github.com/prisma/prisma/releases/tag/3.10.0 ). Running a query against the db I get an error telling me

type EmailMessage { .... error: Model declarations have to be indicated with the `model` keyword`

same error also for EmailSubject my schema:

model Email {
  id            String @id @map("_id") @db.ObjectId
  name          String @unique
  emailMessage  EmailMessage
  emailSubject  EmailSubject
  receiverGroup Receiver[]
  isActivated   Boolean @default(value: true)
  role          String
  btnName       String
}

type EmailMessage {
  id        String
  messageDe String
  messageEn String
}

type EmailSubject {
  id        String
  subjectDe String
  subjectEn String
}

type Receiver {
  id        String
  email     String
  firstName String
  lastName  String
}

What am I doing wrong regarding these embedded documents ? Is there support for embedded document lists but not for embedded documents ?

I tried it and it's working as expected Here's the schema file

generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native"]
}

datasource db {
  provider = "mongodb"
  url      = env("DATABASE_URL")
}

model Email {
  id            String       @id @default(auto()) @map("_id") @db.ObjectId
  name          String       @unique
  emailMessage  EmailMessage
  emailSubject  EmailSubject
  receiverGroup Receiver[]
  isActivated   Boolean      @default(value: true)
  role          String
  btnName       String
}

type EmailMessage {
  id        String
  messageDe String
  messageEn String
}

type EmailSubject {
  id        String
  subjectDe String
  subjectEn String
}

type Receiver {
  id        String
  email     String
  firstName String
  lastName  String
}

Query

import { PrismaClient } from "@prisma/client";

const prisma = new PrismaClient();

async function main() {
  const response = await prisma.email.create({
    data: {
      btnName: "btnName",
      emailMessage: {
        id: "1",
        messageDe: "messageDe",
        messageEn: "messageEn",
      },
      emailSubject: {
        id: "1",
        subjectDe: "subjectDe",
        subjectEn: "subjectEn",
      },
      name: "name",
      role: "role",
      isActivated: true,
      receiverGroup: {
        id: "1",
        email: "<mailto:email@email.com|email@email.com>",
        firstName: "firstName",
        lastName: "lastName",
      },
    },
  });

  console.log(response);
}

main()
  .catch((e) => {
    throw e;
  })
  .finally(async () => {
    await prisma.$disconnect();
  });

Response:

{
  emailMessage: { id: '1', messageDe: 'messageDe', messageEn: 'messageEn' },
  emailSubject: { id: '1', subjectDe: 'subjectDe', subjectEn: 'subjectEn' },
  receiverGroup: [
    {
      id: '1',
      email: '<mailto:email@email.com|email@email.com>',
      firstName: 'firstName',
      lastName: 'lastName'
    }
  ],
  id: '627cfd4cb10b4047615b03f7',
  name: 'name',
  isActivated: true,
  role: 'role',
  btnName: 'btnName'
}

Thank you very much, so this seems to be working with newly created documents, I tried to query all documents from the DB created with prisma1, that didn't work. I want to keep my existing data. 🙂

import { PrismaClient } from '@prisma/client'
 const prisma = new PrismaClient()
 
 async function main() {
   await prisma.$connect()
   const emails = await prisma.email.findMany()
   console.log(emails)
 }
 
 main()
   .catch(console.error)
   .finally(() => prisma.$disconnect())

If your collection name is emails then it has to be defined as

model

in schema file,

type

keyword is reserved for embedded document and shouldn't be used for defining collection.

Ah, so it is not possible to define

model Email @db(name: "emails") {...

using a custom name for the collection ?

You could do that this way

model Email {

@@map("emails")
}

thank you very much 🙂 is it mandatory to use mongodb 4.2+ ? I'm currently using 3.6

I think version 4.2 is a prerequisite: https://www.prisma.io/docs/getting-started/setup-prisma/start-from-scratch/mongodb-typescript-mongodb#prerequisites

I found my problem:

nexus-plugin-prisma@0.35.0" has incorrect peer dependency "@prisma/client@2.23.x"

When I pin the prisma client to 2.23.0 I get these model declaration errors. Do you have any idea how I could resolve this ? I really need nexus-plugin-prisma.

Ah, nexus-plugin-prisma is deprecated in favour of nexus-prisma

yap 🙂 and nexus-prisma is not ready for production which we are using

Are there any records which has id as null?

nope

This should definitely work

const emails = await prisma.email.findMany()

It should return all the emails. Can you create a Bug Report for it here. I think if you add all the fields in select clause then it will work for now.

Did you try this on a existing database created by prisma1 ? Maybe this works for newly created datasets and for what reason ever not for datasets created by P1. 😉

I don't think it matters how data was created as long as it adheres to database schema. But definitely, this is related to P1 -> P2 migration

emailMessage is an embedded field

what error do you get?

so are emailSubject and receiverGroup

Amazing! So you can fetch embedded documents with select clause, right? But this still gives you an error?

const emails = await prisma.email.findMany()

nope, this also works now

The error message could definitely be improved, I'll pass this feedback! 🙌

thank you very much for your help! 🙂