Able to setup Accelerate, unable to setup Pulse. AWS RDS Postgres.
The error : "Prisma Pulse could not reach the specified datasource db url. This could be caused by an incorrect datasource URL or database firewall rules, or certificate issues. This is probably not a problem with Prisma Pulse. The network error was: "Postgres client.connect() is unresponsive."
With the connection string, I can connect using other pgTools from my own computer. My Prisma ORM is using the same connection string and is able to function with Accelerate.
I have followed the instructions in (https://www.prisma.io/docs/pulse/database-setup/aws-rds) and set the rds.logical_replication to 1 (true)....
Why does this function not work?
I'm trying to create a prisma file (/lib/db.ts) to initialize from anywhere in my code when I need it. Why does
$disccount and $use not work and how do i get it to work if it is necessary.
Here is code:
```import { PrismaClient, Prisma } from '@prisma/client'...
Records found that don't exist (Supabase + Prisma)
I've got a very wierd bug I can't figure out.
I've deleted all my records in Supabase for table
upvote, but I am somehow able to find a non-existant record and delete it!
When adding an upvote, I'm checking for a record. If one exists already, I delete it, if not I create one.
Even after clearing the table, it is able to find an existing record and try to delete it (even with a success message) although no record should even exist....
Error validating datasource URL must start with the protocol prisma://
Hello,
I'm having this issue when deploying my Next application to Vercel. Everything works fine locally. I have triple-checked env variables on Vercel and they're the same as my env locally. I also get this error if I build the project and run prod environment locally without deploying to Vercel. Any idea what might cause this; and how to solve it?...
`The Query did not produce a result within the maximum allowed execution time of 10 seconds.`
For a while now we're occasionally getting said error while building our app in GitHub Actions, connecting via Accelerate to MongoDB. The weird thing is, that said collection is basically empty (10 documents) and its documents are tiny. There is no plausible reason that makes this occasionally fail. Can you check what is going on there? We tried adding a cacheStrategy hoping to mitigate this somehow - to no avail. Can you check this request-id for some more detailed logs?
8cb4413f8e688d90
Property does not exist on type..but it clearly does.
```js
const lastIdResult = prisma.descriptionDiff.findFirst({ where: { packageId: thisPackage.id...
const lastIdResult = prisma.descriptionDiff.findFirst({ where: { packageId: thisPackage.id...
