Checklist for migration of underlying database from AWS RDS to Azure
Error with method update: Urgent please
Why are client files generated in node_modules and what does that mean for production builds?
node_modules so they are not in our repositories. Obviously this makes our repos much lighter which is great, but presumably every time we make a database change, we need to not only deploy it, but then each production server needs to regenerate its client files?
Now if the schema files are in source control and the version of prisma/client is pinned in package.json then the output of the file generate should be the same every time, but the fact that I can't guarantee to my boss exactly what code we have running in production, the commit hash for that code, and the test results for that commit hash makes me very uneasy....How to have @createdBy and @updatedBy annotation in prisma schema (like @updatedAt)
user.idin each create/update method of each of my entities is cumbursome. In spring data rest, this is how they do auditing:
```ts...Issue with generating prisma client
Inconsistency in not generating prepared statements when using Prisma Accelerate
Module '"prisma/prisma-client"' has no exported member 'PrismaClient'.
SqlServer $queryRaw with 'in' operator
const arr = ['john', 'tony', 'sarah']
I'm trying to do select * from table where name in (${Prisma.join(arr)})
not returning any result, but if I hard code those values it works fine
when I do console log using array join without prisma join it returned "/'john/',/'tony/',/'sarah/'", might be the problem here ?...Implicit many-to-many problems
createMany doesn't include relational fields? I'm too busy to look into it further, but here is the updated code which succeeded for anyone that might be wondering:
```ts
const dealers = () => {
const dealers: Prisma.DealerCreateInput[] = [];
...Prisma keeps pasting incorrect schema
prisma and @prisma/client are on ^5.18.0
schema.prisma...Upgrading from Prisma 1
prisma@2.0.0 but when I try to run yarn prisma init to setup the new project I get "Error: Unknown binaryTarget debian-openssl-3.3.x and no custom binaries were provided". How do I proceed?
I've tried installing prisma@3.13.0 as suggested in this question but still get the same error.
I'm running with yarn on Node 16 on EndeavourOS (Arch). I have openssl 3.3.1 package installed also....Understanding Prisma Pulse
Invalid error message when using transactions
Prisma gets very slow...
Return type from Prisma query
findMany()
For example, what in this case the variable source type would be?
const sources = await prisma.source.findMany()...Multi-tenant approaches
check for multiple conditions on the same field
Pulse Type
Serving HTTPS from Prisma Client
Prisma migrate deploy doing modification in node_modules after upgrading prisma
npx prisma migrate deploy in a docker image with limited right
In 5.17 i had no issue doing this but after upgrading to 5.18 i have this error:
Error: Can't write to /home/node/node_modules/@prisma/engines please make sure you install "prisma" with the right permissions.
I can't allow my user node to do modifications inside node_modules and i don't understand why this command is now doing writes...