self-relation

Prisma Connection Pool
9 by default.
This low amount of connection pool making our application very slow, espacially because we currently have only one instance of our backend.
...What are the best practices for using Postgres array functions within a Prisma query?
cardinality("comments") AS "commentsCount" in my SELECT clause, but I'd prefer not to have to make the entire query raw. Is there some way to get around this? I'm imagining something like the following:
```
prismaService.posts.findMany({
select: {...Issue with prisma optimize
0.10.0?...using prisma $extends to add fields to a model, whats the best practice for TS?
Does it make sense to create an explicit one-to-many relation?
Alternative to solving optimistic concurrency issue without version field
version field and ask about it in the where clause when updating a model:
```
const userEmail = 'alice@prisma.io'
const movieName = 'Hidden Figures'...Can't use dotenv and ws for edge runtime in authjs middlware. Help any solutions?
Prisma ORM DocumentDB AWS
Error: PrismaClientUnknownRequestError:Invalid `prisma.user.groupBy()` invocation:
``ts
Error: PrismaClientUnknownRequestError:
Invalid prisma.user.groupBy()` invocation:
...
Connections are over connection limit
?connection_limit=30) but the connections go to around 70 - 80. You can see it from the graph. I already made sure if the data from the graph is correct by using this query.
```sql
SELECT
client_addr,...
Prisma type inference is returning weird types
Issues with Prisma 5.3.1: OpenSSL Version Mismatch during Build and Runtime in Docker
prisma client generates model with no create
Type 'Promise<string>' is not assignable to type 'string'

Count with distinct
I/O error: Device or resource busy
``
{
"success": false,
"message": "\nInvalid prisma.pickaxeUser.findUnique() invocation:\n\n\nRaw query failed. Code: unknown. Message: Kind: I/O error: Device or resource busy (os error 16), labels: {"RetryableWriteError"}`"...Convert LONGTEXT to JSON with prisma db pull
10.6.18-MariaDB database and whenever I'm trying to set the column type to Json it changes to LONGTEXT but I already know I can't change that so my question is if can I somehow force the prisma db pull command to see LONGTEXT as JSON instead so I don't need to manually change that every pull?npx prisma generate wont update the Product model.
Otel integration