I’m unable to create a Prisma project. It errors each time. We updated our Database to a new MongoDB instance. It times out while loading the new project on the final step then breaks whenever you open the project.

Please advise ASAP. Website is down until this is fixed.

Hello guys! I'm curious why I can't make requests to specified in

.env

db with prisma methods. All works fine until today, and now prisma giving error "Authentication failed against database server at

localhost

, the provided database credentials for

postgres

are not valid" But yesterday all works fine. Why this can happen? I check db with psql tool and seems like db is up and running, because I can make requests to it, but nor from prisma.

👉 Amplication - an interview with Yuval Hazaz -- -- Checkout our interview from WNIP with Amplication founder and CEO, Yuval Hazaz. Find out how Amplication is using Prisma to help professional developers avoid repetitive coding tasks.

When will prisma bring out full support for MongoDB?

Hi, is there an alternative to graphql-yoga using nexus-plugin-prisma ? I can't get v2 of graphql-yoga running due to incompatibilities between nexus-plugin-prisma and nexus.

Decided to just roll my own DB. From an outside perspective, Prisma was supposed to make things easier but so far it's made things harder for me. Dealing with Prisma + Nexus is super confusing. And I was getting bugs from the auto-generated schemas that were hard to debug.

Is anyone else doing integration testing using Prisma (or any sort of test where you are using the live prisma client)? I’m finding that it often gets overwhelmed with connections. Also when I call

prisma.$disconnect()

it’s taking around 30 seconds to a minute.

Are ANY Prisma team members on who can help?? We need our website operational.

Please, we can't be down for days on end like this

Hi 👋 Do any of you guys use Playwright along with Prisma for db setup/cleanup?

I just (nearly) finished the tutorial from here: https://vercel.com/guides/nextjs-prisma-postgres. The final deployment fails when I try to login (e.g. authenticate with github) with: Server error There is a problem with the server configuration. Check the server logs for more information. The error is as a result of POST https://patty-harris-blogr-nextjs-prisma.vercel.app/api/auth/signin/github. I've checked my server and OAuth setup and I don't see where the mistake is located - the Authorization callback URL, client ID and secret look correct. Any suggestions? Also, where are the server logs located? TIA Never mind - I redeployed and now it's working....odd.

hi, guys, I'm having trouble creating the yyyy-mm-dd date format in PG, can anyone help me? model Subscription { id String @id @default(uuid()) @db.VarChar(250) idPlan String @db.VarChar(250) plan Plan @relation(_fields_: [idPlan], _references_: [id]) //relacionamento idClient String priceAll Decimal @db.Decimal(10, 2) status Boolean paymentMethod String startDate DateTime @db.Date finishDate DateTime @db.Date } Argument finishDate: Got invalid value '2023-02-20' on prisma.createOneSubscription. Provided String, expected DateTime or Null. Argument startDate: Got invalid value '2022-02-20' on prisma.createOneSubscription. Provided String, expected DateTime or Null.

hi, I’m trying to use the

upsert

method with a multi-column unique constraint, e.g.:

// schema.prisma
model X {
  id        ...
  ...
  email     String
  subdomain String

  @@unique([email, subdomain])
}

// api
const upsertX = async params => {
  const { email, subdomain } = params;
  const upsertedX = await prisma.x.upsert({
    where: { email_subdomain: { email, subdomain } },
    update: { ... },
    create: { email, subdomain, ... },
  });
};

for some reason, the

upsert

call always runs for a long time and times out. I tried using

prisma.x.findMany({ where: { email, subdomain } })

instead and that seems to work fine… but shouldn’t the unique constraint make querying by

email_subdomain

faster (or at the very least, it shouldn’t time out). am I missing something?

Does Prisma ONLY work with serverless MONGODB collections?

Any idea why this is happening

Why is this happening

I will pay for someone to tell me exactly how to fix at this point. DM

👋 Hello, everyone! Anyone using/tried to use Prisma with Azure Cosmos DB API for MongoDB? I've used in the past with Mongoose and wanna know if one face a particular problem within this stack. Thank you all! Happy coding.

any way to define a

@@unique(...)

with a

COALESCE(field, 'value-if-null')

field? (like on this - https://stackoverflow.com/a/8289327/4167590)

I reach to a point on where I need some external help. I'm trying to use prisma to feed two different apps that are hosted in the same monorepo. I'm using turborepo as my mono and one app is a web app, and the other one is a terminal (CLI). Both are supposed to the same prisma schema and generated client to interact with the DB (postgres) so I thouhg it would be nice to abstract it an place prisma into it's own shared library in the mono. All in all, this was thought as very simple but it is giving me a lot of problems. Do you know if there is an example fo prisma working kind of like this way under a mono to where I can look for?

Hi Prisma, I've been involved in a project recently that is using Hasura and it blew my mind on how all the graphql queries, mutations, subscriptions and filters are automatically created just by inspecting the database. Prisma has been my favorite ORM for a while and I'm wondering if there's any library or utility in Prisma environment or something close we can use to replicate the features on Hasura Thanks

Does someone has a tutorial on how to create graphql inputs for prisma autogenerated DTO's in nestjs using this library https://www.npmjs.com/package/prisma-nestjs-graphql??

I cant really understand how to properly use connect on create or create nested objects

👋 Hello Prisma Community! The Prisma team is currently attending the Prisma offsite (Mon May 16th > May 20th) so our responses will be delayed. We count on our ✨ amazing community ✨ to help each other and we'll do our best to answer questions throughout the breaks in the week and next week. Thank you for your understanding! 💚

Prisma Data Browser throws this error. Is it known to you already?

Hi all I’m soon to board a long hault flight and trying to get the prisma docs running locally. When I try to run

npm install

i get an

ERESOLVE

error. Any ideas?

I’m trying to create a system of shared keys across my app. The idea is that there’s a central store of keys in the database and: 1. A server can request an available key, which is returned and marked as in use. 2. A server can relinquish its key (or the hold on the key will eventually expire), which will mark it as available. 3. If no keys are available the server can generate a new set of keys to repopulate the table (these keys require some specific formatting logic so I don’t think the can be generated inside the database) I see Prisma supports transactions, but they seem to be per request (i.e. they are atomic within a single request but if two separate servers simultaneously request a key, return a key, etc. you can get a data race). So how would one implement this using Prisma? P.S. - I’ve never worked with databases before (my background is in game, mobile and front-end development) so feel free to point out things that should be glaringly obvious 😉 P.P.S. - The reason I think transactions are not safe across multiple requests is this issue: https://github.com/prisma/prisma/issues/3242