I have an authentication table and users table with one-one relationship and i did with findMany and is but i found some strange because i need to be unique in my database and with findUnique doesnt work with is

Hi Prisma Family, I cannot seem to create a new project on Prisma Data Platform, clicking the ‘New Project’ button doesn’t do anything. Anyone know how to resolve this?

Hello, Im having a very hard time creating this SQL statement with Prisma. Would anyone know how it can be done?

SELECT *
FROM "token"
INNER JOIN "user" u on u.user_id = token.user_id
WHERE u.email = '<mailto:abc@abc.com|abc@abc.com>'

actually im trying to update instead of select

i tried this:

await prisma.token.update({
    data: {
        user: {
            connectOrCreate: {
                where: {
                    email: user.email
                },
                create: {
                    token: user.token
                }
            }
        }
    },
    include: {
        user: true
    }
})

The logic is update "token" column where "user_id" is fk to "user" table...find "token" based off "email" in "user" table... hope it makes sense

im not sure whats wrong with my logic here.. so i dont have any records in my token table so far... using upsert should find record if it exists where user_id = 1 If it finds row with user_id = 1 then it should update the token column.. if it doesnt exist, then create: { user_id and token } and insert

await prisma.token.upsert({

where: {

'user_id': dbUser.user_id

},

data: {

'token': refreshToken

},

create: {

'user_id': dbUser.user_id,

'token': refreshToken

}

});

wrapping my prisma.table.update() (and all other CRUD calls) with try and catch just gives me client version when i output catch error. whats the recommended way

is it possible to just throw in SQL statements instead of using this json mannerism? got a coworker whose using this plugin and its extremely difficult for me. pure SQL works for me but would still like to use the prisma schema for his sake. is it possible?

awesome thanks so much!

Hi all -- I'm having trouble following the guide for the expand-contract pattern in the context of a rolling deploy where two versions of my prisma client are running at the same time. Steps 1-6 work just fine, but Step 7 asks me to remove a column from my schema. When I do that, the new prisma client expects the column to be removed whereas the old prisma client expects the column to be present. During the rolling deploy, code reliant on the old prisma client will throw errors, even if I don't refer to that column anywhere in my code. I'm guessing because it's performing a

SELECT *

, and trying to map column values into required fields in the resulting JS object. Any advice on what to do here? Is there a way for me to exclude a field from my prisma client without modifying the underlying database schema?

Has anyone else had problems with

@db.Decimal(XX, 5)

? For some reason when I set my data to 5 decimal places, the values come out like

12.000000000000002

. Not only is it adding a float rounding error, they have too many decimal places. Setting it to 2,3,4,and 6 work fine. I haven’t checked above that point.

This message was deleted.

Hi building a home application. We have Home model { id name String } and Facility { id name String } The facilities are fixed and will be unversal for all homes. Example Pool, Kithcen, Shower etc. The homes can have none or all of the facilites. How should this many to many relationship be setup?

Anyone using Webstorm? What do you use to write

schema.prisma

? This plugin really sucks… https://plugins.jetbrains.com/plugin/14240-prisma

question on Cascading deletes with SQLite. I have a few models and I if I want to delete a Player, I want all other associated data to be deleted as well

model Player {
  id        String        @id
  username  String?
  createdAt DateTime      @default(now())
  updatedAt DateTime      @default(now())
  losses    Match[]       @relation("Losses")
  resigned  Match[]       @relation("Resigned")
  wins      Match[]       @relation("Wins")
  moves     Move[]
  matches   PlayerMatch[]
  rolls     Roll[]
  lastLogin DateTime?
}

Heya, bumping my question from yesterday. I'm having trouble following the guide for the expand-contract pattern in the context of a rolling deploy where two versions of my prisma client are receiving production traffic at the same time. Steps 1-6 work just fine, but Step 7 asks me to remove a column from my schema. When I do that, the new prisma client expects the column to be removed whereas the old prisma client expects the column to be present. During the rolling deploy, code reliant on the old prisma client will throw an error like below, even if I don't refer to that column anywhere in my code. Any advice on what to do here? Is there a way for me to exclude a field from my prisma client without modifying the underlying database schema?

Invalid `prisma.user.findUnique()` invocation:
  The column `User.removedField` does not exist in the current database.

I'm using prisma proxy and my schema is outdated, is there a way to update it?

Hello fam! Anyone with a good explanation as to why

contains

fails to match if filter is the first word of text? E.g., Say

description="Chaiwa is a good guy"

, sending

filter: "guy"

matches this record but sending

filter: "chai"

fails. See implementation of the where clause for the query below:

const where = args.filter
    ? {
        OR: [
          {
            description: { contains: args.filter },
            url: { contains: args.filter },
          },
        ],
      }
    : {};

Hello all, I'm trying out a prisma generator called

zod-prisma

but so far it keeps getting stuck at the generation step. Has anybody here experienced this issue?

Hi, interactiveTransaction stopped working for me as of Prisma 3.13. I'm getting the following error: `Error: Failed to convert napi

string

into rust type `String``

at Object.transaction (/usr/src/app/node_modules/@prisma/client/runtime/index.js:41312:64)

at async Proxy._transactionWithCallback (/usr/src/app/node_modules/@prisma/client/runtime/index.js:46414:21)

model Person {
  id   Int    @id @default(autoincrement())
  name String
}

<http://router.post|router.post>('/person', (req, res, next) => {

  prisma.$transaction(async (prisma) => {
    const person = await prisma.person.create({
      data: {
        name: 'A new role',
      },
    });

    // Do something else

    return person;
  }).then(person => res.status(201).json(person))
    .catch(next);
});

Greetings, friends - I’m somewhat new to prisma (loving it so far), so this may be a dumb question, but I couldn’t find the answer in the docs or searching for it. I’m trying to add null values to an integer array in Postgres. I have a simple model defined as

model foo {
  id   String     @id
  bar Int[]
}

when I have:

bar = [0, 0]

and call

prisma.foo.create({
  data: {
    bar
  },

the array is saved in the database, but when I try to set one of the values to null

bar = [null, 0]

I get a vague error

failed: {"clientVersion":"3.12.0"}

I tried turning on extra debug logging, but I’m not getting any useful info. I can also directly update the row directly in postgres without any issues ( … set bar = ‘{null,0}’) Is it possible to set null values in an integer array through prisma? I appreciate any help you can provide.

Hi everyone,

prisma migrate dev

is overwriting a custom migration that I wrote to alter one of my tables, this is the custom SQL script (I first created an empty migration using --create-only):

-- AlterTable
ALTER TABLE "menu-item-translations"
DROP CONSTRAINT "menu-item-translations_menuItemId_fkey",
ADD CONSTRAINT "menu-item-translations_menuItemId_fkey"
FOREIGN KEY ("menuItemId") REFERENCES "menu-items"("id") ON DELETE CASCADE ON UPDATE CASCADE;

After that I ran

prisma migrate dev

but it creates another migration (which i don't want because it removes the cascade behavior, idk why Prisma is doing this???):

-- DropForeignKey
ALTER TABLE "menu-item-translations" DROP CONSTRAINT "menu-item-translations_menuItemId_fkey";

-- AddForeignKey
ALTER TABLE "menu-item-translations" ADD CONSTRAINT "menu-item-translations_menuItemId_fkey" FOREIGN KEY ("menuItemId") REFERENCES "menu-items"("id") ON DELETE SET NULL ON UPDATE CASCADE;

hi there, can someone please help with a few concerns? 1. what’s the best way to track migration history? a. based on the official documentation https://www.prisma.io/docs/concepts/components/prisma-migrate#migration-history, we have list of files in

migrations

folder +

_prisma_migrations

table. it’s kind of ok for working on migrations for 1 person. but, did anyone face any problems with creating a few migrations in 10 PRs? which PR’s migration will go first when we merge? how do you handle the migration history in that case? b. how to make sure that version control work as it expected? for example when 5 engineers works on the same table and created a few PRs that will somehow affect the same table? 2. how to rollback? a. how do we rollback the latest local migration? b. how do we rollback to the specific migration? 3. how to catch migration errors? a. what happened if some migration fails? how do we know and fix it? thanks!

Is this the best place to ask questions regarding prisma? Or is there a help channel devoted to that?

I’m trying to build a POC for work and translate an already existing MongoDB document schema into my

schema.prisma

file. So far it seems relatively straight forward but I have one field that is using a Record utility type in typescript. It’s type is

Record<string, string | number | boolean | null | undefined>

is there a way to translate this into prisma’s schema file?

Hi!! how is everyone

Does anyone know why Prisma tries to overwrite my custom migration script? This looks like a bug to me.

Hi folks, we are running into various jest problems with our prisma. It seems each test-file is creating a new instance of prisma, leading to a major heap size after a while. The prisma instances do not seem to be closed or removed either. Since we can’t share globals in jest (meaning we can’t have a single instance of prisma), did anyone experience this, and figure out a way to circumvent this problem? Example of a jest file:

// Intantiation class in a /src/utils/makeTestPrisma.ts
export const makeTestPrisma = () => {
    if (process.env.NODE_ENV === 'test') {
      const prisma = global.testPrisma || new PrismaClient({
        datasources: { postgresql: { url: 'OUR_URL' } },
      });
  
      global.testPrisma = prisma;
  
      return prisma;
    }
  
    throw new Error('Not possible; only works in Test environment!');
  }


// In a test file, /src/Users/User.test.ts

const prisma = makeTestPrisma();

test(async () => {
   const res = await services.doSomeStuffInDb(prisma);

   expect(res.users).toEqual(2);
});

👋 Hello, team!

Hello ! My model :

model Response {

id       Int      @id @default(autoincrement())

survey   Survey   @relation(fields: [surveyId], references: [id])

surveyId Int

user     User     @relation(fields: [userId], references: [id])

userId   Int

sendAt   DateTime @default(now())

json     Json

}

How to use findUnique on the field user ? I want to get the user with the ID 1