Nested writes don't work on 3rd level with required relation

[nikolasburk]

I have these models:

model Item {
  id           String   @default(cuid()) @id
  createdAt    DateTime @default(now())
  updatedAt    DateTime @updatedAt
  purchaseDate DateTime?
  name         String
  type         ItemType
  locatedIn    Room?
  price        Float?
}

model ItemType {
  id    String @default(cuid()) @id
  name  String @unique
  items Item[]
}

model Room {
  id          String  @default(cuid()) @id
  name        String  @unique
  items       Item[]
  floor       Floor?
  meetingRoom Boolean
}

I now want to create a new Room with new Items which all need an ItemType. However, the nested write arguments are not available for the type field on created Items:

photon.rooms.create({
  data: {
    items: {
      create: {
        type: {  // ... not available
                 // create/connect ... not available
        }
      }
    }
  }
})

[pantharshit00]

I can confirm this.

Here is a reproduction for internal use: https://github.com/harshit-test-org/prisma-photonjs-275

[dpetrick]

This is not reproducible on the engine level, I can write a GraphQL mutation directly against the query engine that allows for creating item types.

[dpetrick]

To elaborate:

• Needed to remove floor Floor? that snuck in :)
• This query works in the query engine:

mutation {
  createOneRoom(data:{
    name: "SomeRoom"
    meetingRoom: true
    items: {
      create:{
        name: "SomeItem"
        type:{
          create:{
            name: "SomeType"
          }
        }
      }
    }
  }) {
    id
  }
}

[janpio]

I adapted the reproduction above to alpha 917:

1. prisma2 init
2. Edit datasource.provider to sqlite, datasource.url to "file:dev.db"
3. Append schema:

   model Item {
     id           String   @default(cuid()) @id
     createdAt    DateTime @default(now())
     updatedAt    DateTime @updatedAt
     purchaseDate DateTime?
     name         String
     type         ItemType
     locatedIn    Room?
     price        Float?
   }
   
   model ItemType {
     id    String @default(cuid()) @id
     name  String @unique
     items Item[]
   }
   
   model Room {
     id          String  @default(cuid()) @id
     name        String  @unique
     items       Item[]
     meetingRoom Boolean
   }

4. prisma2 migrate save --experimental and prisma2 migrate up --experimental
5. Create index.js with content:

   const { PrismaClient } = require('@prisma/client')
   
   const prisma = new PrismaClient()
   
   prisma.Room.create({
       data: {
           items: {
               create: {
                   
               }
           }
       }
   })

This leads to these suggestions:

Is this the expected behavior @nikolasburk and this bug can be closed?

[nikolasburk]

Looks good to me, thanks a lot 🙏