In the first example of the Prisma API docs Mutations section (https://www.prisma.io/docs/reference/prisma-api/mutations-ol0yuoz6go#overview ), if I want to createPost(), is there any way to connect it to an author if I'm not sure whether the author exists or not? It seems like I would want to use an upsert mutation, but the docs say that's only available in an update mutation. Is it possible to nest an update mutation inside of a create mutation?

have you tried it?

Once I'm nesting inside of author, I can only connect or create. Inside that I can provide the name of the author. This works fine for either connecting to an existing author or creating a new one. But if I try to use upsert anywhere inside the createPost mutation, I get syntax errors. I also don't have the option to use the updateAuthor mutation from inside the createPost mutation. So, I'm not really sure how to proceed. I could try the updatePost mutation. But that's not really quite what I want.

Can you share your service endpoint so I can follow along? 🙂

Yep. Thanks! I'm deployed locally, though. I'm totally new to this. Need to figure out how to deploy to prisma cloud first.

You can also share your datamodel

type Album { id: ID! @unique title: String! artist: Artist! art: String! year: String! rating: Int! owner: User! } type Artist { id: ID! @unique name: String! @unique works: [Album!]! } type User { id: ID! @unique username: String! @unique collection: [Album!]! }

so which mutation are you then trying?

phillip-gray-ccefc1/album-collector-api/dev

Thanks a lot for bringing this up, @thephilgray. I think adding the

upsert

as a nested mutation inside

createX

is a great idea. I created this feature request, including the current workarounds that I am aware of: https://github.com/graphcool/prisma/issues/2194

Awesome. Thanks!

You should be able to apply the first one I mentioned 🙂 Let me know if you have any questions about it!

It worked great! I also ended up implementing the same workaround solution for another similar feature. Thanks, again!