Chris
09/07/2021, 7:25 PMAlexandr Bordun
09/08/2021, 6:58 AM✔ Generated Prisma Client (3.0.1) to ./node_modules/@prisma/client in 230ms
You can now start using Prisma Client in your code. Reference: <https://pris.ly/d/client>
import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()
warn Prisma 2.12.0 has breaking changes.
You can update your code with
`npx @prisma/codemods update-2.12 ./`
Read more at <https://pris.ly/2.12>
I’m mostly concerned about Prisma 2.12.0 has breaking changes
anyone knows the reason/solution for this?Hector
09/08/2021, 3:23 PMPascal Sthamer
09/09/2021, 12:36 PM➤ YN0007: │ prisma@npm:2.30.3 must be built because it never has been before or the last one failed
141
➤ YN0007: │ @prisma/client@npm:2.30.3 [2a8e9] must be built because it never has been before or the last one failed
142
➤ YN0000: │ @prisma/client@npm:2.30.3 [2a8e9] STDOUT Prisma schema loaded from prisma/schema.prisma
143
➤ YN0000: │ @prisma/client@npm:2.30.3 [2a8e9] STDERR info The postinstall script automatically ran `prisma generate`, which failed.
144
➤ YN0000: │ @prisma/client@npm:2.30.3 [2a8e9] STDERR The postinstall script still succeeds but won't generate the Prisma Client.
145
➤ YN0000: │ @prisma/client@npm:2.30.3 [2a8e9] STDERR Please run `yarn prisma generate` to see the errors.
146
➤ YN0000: │ @prisma/client@npm:2.30.3 [2a8e9] STDOUT
It works fine locally. Anybody has an idea?Mischa
09/10/2021, 3:18 PMKul
09/11/2021, 7:56 AMRamon Pans
09/11/2021, 11:11 AMRamon Pans
09/11/2021, 1:20 PMcreate
method not existing?Ben Ezard
09/11/2021, 4:18 PMPrismaClient
, each of which hangs on to some memory even after $disconnect
is called
This appears to be backed up by the warning messages that I get saying Already 10 Prisma Clients are actively running
I'd expect $disconnect
to kill and release the memory of the underlying engine instance, but I assume there's a good reason why this isn't done
What's the recommended way of handling this please? Sadly it's private code so I can't link to a repo, but I'm happy to provide any requested details where possibleCasey Chow
09/13/2021, 9:53 PMRussell Ormes
09/14/2021, 9:21 AMGautam Paranjape
09/14/2021, 6:19 PMChris
09/15/2021, 7:07 PMUserCreateManyInput
(really, anything TCreateManyInput
) is used not for performing actions against the db, but for declaring the type of data returned from a raw query. Is this an appropriate use? The name certainly leads me to believe there could be problems with thisChris
09/15/2021, 7:46 PMUser
would be the path to take (when the query does in fact correspond to this)Mischa
09/16/2021, 4:51 PMHarsha MV
09/18/2021, 5:17 PMHarsha MV
09/18/2021, 5:17 PMbind message supplies 1 parameters, but prepared statement \"s1\" requires 2
Mischa
09/21/2021, 7:10 AMerror TS2742: The inferred type of 'doStuff' cannot be named without a reference to 'myapp-repo/node_modules/.prisma/client'. This is likely not portable. A type annotation is necessary.
easily worked around but strange.
I'm trying to infer return types of functions doing prisma queries across packages so I guess that doesn't work anymoreLukas Heddendorp
09/22/2021, 8:52 AM2021-09-22T08:32:41.838273674Z (node:27) UnhandledPromiseRejectionWarning: Error:
2021-09-22T08:32:41.838296175Z Invalid `prisma.user.findFirst()` invocation:
2021-09-22T08:32:41.838369076Z
2021-09-22T08:32:41.838374676Z
2021-09-22T08:32:41.838378576Z Timed out fetching a new connection from the connection pool. (More info: <http://pris.ly/d/connection-pool>, Current connection limit: 3)
2021-09-22T08:32:41.838395576Z at PrismaClientFetcher.<anonymous> (/usr/src/app/dist/apps/api/main.js:39266:31)
2021-09-22T08:32:41.838400576Z at Generator.throw (<anonymous>)
2021-09-22T08:32:41.838404576Z at rejected (/usr/src/app/node_modules/tslib/tslib.js:115:69)
This is the issue that keeps popping up, I'm guessing the findFirst isn't even the problem but rather my connections.
I'm running this on the azure app service so I was also wondering if I could increase my connection limit or if that's useless without more cpu cores.
Grateful for any hints from you side 🙂Peter Kim
09/23/2021, 6:45 AMLukas Heddendorp
09/23/2021, 10:23 AMShubham Patil
09/25/2021, 6:23 PMShubham Patil
09/25/2021, 6:24 PMShubham Patil
09/25/2021, 6:24 PMShubham Patil
09/25/2021, 6:25 PMShubham Patil
09/25/2021, 6:25 PMJohn Peña
09/27/2021, 7:47 PM"cached plan must not change result type"
Lukáš Stuchlík
09/29/2021, 6:45 AMprisma:query
selects that operate on a single table with ID constraint, instead of joins through foreign keys.. Is it because of performance? are foreign keys utilized in any other way than referential integrity? can we speed up such selects in any way?Michael B
09/29/2021, 11:38 AMmodel User {
email String?
}
and requesting users in the client
const users = await prisma.users.findMany({
where: {
NOT: {
email: {
equals: null,
},
},
},
})
Is it possible to get a returned type of?
{ email: string }[]
The current return type I am getting is
{ email: string | null }[]