Sorry for this, I have changed and found another way to do this. If anyone was curious on how i changed it (for future use if anyone gets stuck and gets the same results like this)

    const prisma = new PrismaClient()
    const { username, email, hashPassword } = await request.json();
    let verified = crypto.randomBytes(32).toString('hex');

    const userExist = await prisma.users.findFirst({ where: { OR: [{ username }, { email }] } })
    if (userExist === null) {
        await prisma.users.create({ data: { username, email, hashPassword, verified } })
        return new NextResponse('Success!', { status: 201 })
    } else {
        return new NextResponse("Sorry, username and or email already exists!", { status: 500 })
    }

Hi @TheLexoPlexx 👋

The second version is creating a new Abwesenheit object using the create method, and then connecting it to an existing Zeitraum object using the connect method. it guarantees that only one Abwesenheit object is associated with a given Zeitraum object, as required by the relation between the two models. However in the first version, you are using the create method to create a new Abwesenheit object and associate it with an existing Zeitraum object, using the abwesenheit field. However, this approach can cause a conflict if the Zeitraum object already has an associated Abwesenheit object.

If I understand your question correctly, the request body may optionally contain an id or be undefined. If the id is present in the request, you want to update the corresponding record. If it isn't, you want to create a new record.

upsert functionality requires a unique identifier that can be used by the database to check whether there is a matching record. The database will then decide what to do. However with an undefined value, prisma cannot work.

You could use a key that will not exist in the database in case the value of id is undefined to make upsert insert the record in this case.

await prisma.profile.upsert({
  where: { id: id || '' },
  // ...
});

Or you could differentiate the cases and treat them appropriately:

if (id) {
  await prisma.profile.update({
    where: { id },
    data: {
      username,
      about,
      // ...
    },
  });
} else {
  await prisma.profile.create({
    data: {
      username,
      about,
      // ...
    },
  });
}

You might want to think about the case that there is an id given in the body, but it does exist in the database. Do you want the update to fail and reply with an error? Or do you want the database to silently insert? Then use upsert instead of update above.

This seems to work:

where: {
  id: args.id || 0,
},

If an id is provided it will set it, otherwise it will use id 0 which does not exist so it will create a new record.

Hey @DivMode 👋,

I wasn't able to recreate this one with the given info.

Would you mind providing some sample data so I can try to reproduce the error?