I've got the following mutation resolver;

async createCheckIn(parent, { title, location }, context) {
    const userId = getUserId(context);
    const { geonameId, ...rest } = location;
    if (!location || !geonameId) {
      throw new Error(`CheckIn must include a valid location`);
    }
    return context.prisma.createCheckIn({
      title,
      location: {
        upsert: {
          where: {
            geonameId
          },
          update: { ...rest },
          create: { ...location }
        }
      },
      public: true,
      user: { connect: { id: userId } }
    });
  }

But I'm getting an error that says "Field 'upsert' is not defined in the input type". Does anyone see what I'm doing wrong here?

whats the input type of location

In my schema.graphql I have;

type Mutation {
  createCheckIn(title: String, location: LocationInput!): CheckIn!
}

type CheckIn {
  id: ID!
  public: Boolean
  title: String
  location: Location!
  user: User!
  createdAt: String!
}

type Location {
  id: ID!
  geonameId: String
  city: String
  regionName: String
  countryName: String
  latitude: String
  longitude: String
  checkIns: [CheckIn!]
}

input LocationInput {
  geonameId: String
  city: String
  regionName: String
  countryName: String
  latitude: String
  longitude: String
}

you mean your prisma.datamodel?

prisma.datamodel has;

type CheckIn {
  id: ID! @unique
  createdAt: DateTime!
  updatedAt: DateTime!
  public: Boolean @default(value: "true")
  title: String
  location: Location! @relation(name: "CheckInToLocation")
  user: User! @relation(name: "UserCheckIn")
}

type User {
  id: ID! @unique
  email: String! @unique
  password: String!
  name: String!
  checkIns: [CheckIn!] @relation(name: "UserCheckIn")
  following: [User!] @relation(name: "Follow")
  followers: [User!] @relation(name: "Follow")
}

type Location {
  id: ID! @unique
  geonameId: String! @unique
  city: String
  regionName: String
  countryName: String
  latitude: String
  longitude: String
  checkIns: [CheckIn!] @relation(name: "CheckInToLocation")
}

you have type overwritten in your schema...

I don't understand what you mean

don't the schemas get merged

I don't think so... I got here by following https://www.howtographql.com/graphql-js/0-introduction/

you have location defined in both

AFAIK, datamodel is for Prisma and schema is for graphql-yoga

yes I know

Everything in datamodel.prisma is also in my schema

but on the default setup they get merged

Yes, and so is User and so is CheckIn

weird, I thought you specifically couldn't do that

It's been working for me so far... but this upsert thing isn't working

if I have a type in prisma.datamodel it is pulled in automatically to schema.graphql through the schema merge

What can I look for in the playground?

well I goto the prisma playground

How do I find that?

have you used the playground?

But how do I look for functions?

they are on the right

This is what I see

should be a list of mutations and queries

Yeah...

yea, you dont have upsertLocation

No, it's my GraphQL server... there's a separate playground for Prisma?

yes

How do I access that?

Oh, found it...

yea

I see this;

input LocationUpsertWithoutCheckInsInput {
  update: LocationUpdateWithoutCheckInsDataInput!
  create: LocationCreateWithoutCheckInsInput!
}

playing with mine actually

Hmph.... That's frustrating... where did you get that information?

so they must make you create seperately

Ah, I see

and create

So in my resolver function could I do

context.prisma.createLocation()

and then

context.prisma.createCheckIn()

? In the same function?

of course

Cool cool

yea

Nice

np

It's working! Thanks so much for your help @CCBCodeMonkey 🙂 This was the last piece I needed to finish what I set out to accomplish this morning on my side project

no prob! have a good night