I’m trying to update a relational field:

prisma.practitioneer.update({
    where: {
      userID,
    },
    data: {
      image: {
        update: {
          where: { id: imageID },
          data: {
            image: image.data,
            type: image.type,
          },
        },
      },
    },
  });

But I’m getting this error:

Unknown arg `image` in data.image for type practitioneerUncheckedUpdateInput. Did you mean `imageID`? Available args: …

If I try to change the query to (which is obviously wrong):

prisma.practitioneer.update({
    where: {
      userID,
    },
    data: {
      imageID: {
        update: {
          where: { id: imageID },
          data: {
            image: image.data,
            type: image.type,
          },
        },
      },
    },
  });

I get the same error, only now it’s suggesting the correct field, the one it previously said it didn’t find:

Unknown arg `imageID` in data.image for type practitioneerUncheckedUpdateInput. Did you mean `image`? Available args: …

New Course: Fullstack App Using Next.js, GraphQL, TypeScript & Prisma https://www.prisma.io/blog/announcing-upcoming-course-8s41wdqrlgc7 We're thrilled to announce that we're working on a new course where you'll learn how to build a fullstack app using Next.js, GraphQL, TypeScript, and Prisma!

Hey guys, I'm new to this channel so forgive me if this is the 100th time this question has been asked. Is there any update on the Aurora Data API integration? https://github.com/prisma/prisma/issues/1964

hello, when I delete a record that has an optional relation to another model, the optional relation's records also get deleted, any way to prevent this?

model User {
    ....
    memos Memo[]
}

model Memo {
    userId String?
    user User? @relation(fields: [userId], references: [id])
}

on version 2.22 when I tried to delete a record which has a required relation i would get an error with the code

P2014

and now on 2.26 I get

P2003

. Is this change related to the new update with

referentialActions

?

foobar1

?

Hi, version 2.26.0 with pnpm breaks spectacularly, even creates a package-lock.json and tries to overwrite node_modules or something? I created a small repo with the issue with instructions/screenshots in the README https://github.com/PabloSzx/pnpm-prisma-bug and maybe it's important to say that version 2.23.0 everything works fine, every project that uses prisma I have to pin the version to that

Hi, hope you're doing well! I have created a seeder function but it seems like it's not working. Here is the code

import faker from "faker";
import { PrismaClient } from "@prisma/client";
const prisma = new PrismaClient();

export async function seed() {
  const user = await prisma.user.create({
    data: {
      lastName: faker.name.lastName(),
      firstName: faker.name.firstName(),
    },
  });

  const post = await prisma.post.create({
    data: {
      userId: user.id,
      body: faker.lorem.slug(300),
    },
  });

  console.log({ post, user });
}

The information is not being logged and is not being saved to the database... Is there something wrong or am I doing something not correctly?

I have a Post and Comment models. I want to create a Vote model I can use for my Posts/Comments. How would I achieve something like this? I'm having a hard time wrapping my head around it

hey all, im having some trouble running a migration script inside of a github action. I am trying to connect to a google cloud sql database with a connection string. (I am able to use the same connection string to connect via GUI and command line, so I know it works), however inside the github action after running

npx prisma migrate deploy

I get this error:

Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "postgres", schema "public" at "IP"
Error: P1001: Can't reach database server at `IP`:`5432`

Please make sure your database server is running at `IP`:`5432`.
Error: Process completed with exit code 1.

anyone ever run into this or have any thoughts on why this might be?

Please, Please help me. This is killing my time. this is my model for User:

model User {
  id                          String                      @id @default(cuid())
  password                    String?                     @db.VarChar(255)
  phoneNumber                 String                      @unique
  createdAt                   DateTime?                   
  updatedAt                   DateTime?                    
  deletedAt                   DateTime?
}

and when I do this:

await prisma.user.create({
        data: {
          password: "password",
          phoneNumber: "+4081824712",
        },
      });

I get this error:

Invalid `prisma.user.create()` invocation:

{
  data: {
    createdAt: '2021-06-30T00:41:32Z',
+   phoneNumber: String,
?   id?: String,
?   password?: String | null,
?   updatedAt?: DateTime | null,
?   deletedAt?: DateTime | null
  }
}

Argument phoneNumber for data.phoneNumber is missing.

Note: Lines with + are required, lines with ? are optional.

I don’t see any problem with my code..

is it some kind of bug ?

Is there a clean way to do optional relations in the case where sometimes the relation is linked to one table but other times it is linked to another. For example:

model Circle {
  id         Int        @id @default(autoincrement())
  name       String
  shape      Shape?
}

model Square {
  id              Int        @id @default(autoincrement())
  name            String
  shape           Shape?
}

model Shape {
  id        Int      @id @default(autoincrement())
  type      String
  typeId    Int
  circle    Circle?   @relation(fields: [typeId], references: [id])
  square    Square?   @relation(fields: [typeId], references: [id])
}

I think what I am looking for is "optional" relation

Does

create

option in

upsert

update if there is an existing record?

so if we're not sure if the record exists then should we provide the same object to

create

and

update

The new

referentialActions

breaks current Studio release 😞 https://github.com/prisma/studio/issues/716

Error starting Prisma Client: {
  "message": "Schema Parsing P1012\n\nGet config \nerror: The preview feature \"referentialActions\" is not known. Expected one of: microsoftSqlServer, orderByRelation, nApi, selectRelationCount, orderByAggregateGroup, filterJson\n  -->  schema.prisma:9\n   | \n 8 |   provider        = \"prisma-client-js\"\n 9 |   previewFeatures = [\"orderByRelation\", \"nApi\", \"referentialActions\"]\n   | \n\nValidation Error Count: 1\n",

New error this morning on https://cloud.prisma.io/

Hey! I have a question about implementing middleware in a NextJS app. I’m using this approach to include Prisma in the app:

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

// add prisma to the NodeJS global type
interface CustomNodeJsGlobal extends NodeJS.Global {
  prisma: PrismaClient;
}

// Prevent multiple instances of Prisma Client in development
declare const global: CustomNodeJsGlobal;

const prisma = global.prisma || new PrismaClient();

if (process.env.NODE_ENV === 'development') global.prisma = prisma;

export default prisma;

Is there any best practice way of including a Prisma middleware in a NextJS app? The docs only mentions an express app.

hi, I need help with building a matrimonial site, I prefer to choose - language - typescript - frontend - nextjs - backend - prisma 2 + typeGraphql. is it a good choice? any suggestion

Hey! I am getting below error

This is my resolvers

Mutation: {
    ...buildMutationResolvers(prisma.mutation),
  },
  Subscription: {
    submission: {
      subscribe: () =>  pubsub.asyncIterator(['SUBMISSION_CREATED', 'SUBMISSION_UPDATED', 'SUBMISSION_DELETED'])
    },
    submissionReview: {
      subscribe: () => pubsub.asyncIterator(['WAR_CREATED', 'WAR_UPDATED', 'WAR_DELETED'])
    }
  },

This is how I am building the mutation resolvers

const buildMutationResolvers = (methods) =>
  Object.entries(methods).reduce(
    (resolvers, [queryName, queryFunc]) => ({
      ...resolvers,
      [queryName]: async (parent, args, context, info) => {
        const label = getPublishLabel(queryName)
        // const data = await queryFunc(args, info)
        if(label) {
          pubsub.publish(label[0], { [label[1]]: args});
        }
        return queryFunc(args, info)
      },
    }),
    {}
  );

method to get the label

const getPublishLabel = (mutationName) => {
  const labels = {
    createSubmission: ['SUBMISSION_CREATED', 'submission'],
    updateSubmission: ['SUBMISSION_UPDATED', 'submission'],
    deleteSubmission: ['SUBMISSION_DELETED', 'submission'],
  }

  if(!!labels[mutationName]) return labels[mutationName]
  return false
}

What am I doing wrong ?

how can I get a record from the db by providing an enum argument instead of id? It is the id that I want to figure out and I want the client to provide an enum instead. Im thinking something like this:

const device = await prisma.device.findUnique({
      where: {
        deviceType: {
          contains: args.data.deviceType
        }
      },
      connect: {
        user: {
          id: userId
        }
      }
    });

This obviously doesnt work but hopefully you would get the idea.

Hello prisma team, I have a doubt with respect to raw queries. So I have the below model (Using

Postgres

as DB)

model Test {
  id String @id @default(uuid())

  name           String

  // common fields
  createdAt DateTime @default(now()) @map("created_at")
  updatedAt DateTime @default(now()) @updatedAt @map("updated_at")

  @@map("test")
}

and using below code snippet in node js.

async function update() {
      // Node js
      // Current state of the row in the DB
      await model.test.findUnique({ where: { id: 1 } });
      // { id: 1, name: "current_value", updated_at: "2021-06-30T11:00:16.291Z", created_at: "2021-06-30T11:00:16.291Z"}
      await model.test.updateMany({ data: { name: "after_update" } });
      // { id: 1, name: "after_update", updated_at: "2021-06-30T12:00:16.291Z", created_at: "2021-06-30T11:00:16.291Z"}
      await model.$queryRaw(`UPDATE test set name = 'updater_after_raw'`); // @rawQuery
      // { id: 1, name: "updater_after_raw", updated_at: "2021-06-30T12:00:16.291Z", created_at: "2021-06-30T11:00:16.291Z"}
    }

Here after

@rawQuery

,

update_at

field is not being updated. Couldn't understand this behaviour. Is this intentional or any issue? Expected behaviour - It should update the

updated_at

field when I am writing raw update query in prisma.

Hi, Is there a way to filter by a string type field, with contains_every ?

Any way to update a field on connect? Seems like the problem is I can’t update a relational field inside a create.

prisma.user.create({
  someRelationalField: {
    connect: {
      userId: userID
    },
    update: {
       // Is this possible?
    }
  }
})