riivault_/ENTITY 042
● LiveproductORMs / data accessrepo:prisma/prismanpm:prismase_tag:prisma
Entity drill-down · last 180 days ·30d90d180d

Prisma

Hype · Discussion moved +21200.0% while downloads moved -20.5%. (as of 2026·08·12)

Narrow: 31 distinct voices behind 212 mentions.

Who is talking
0.15
31 distinct voices across 212 mentions

Distinct voices per mention. 1.00 means every mention came from a different person; a low number means a handful of people are driving the volume. Authors are counted once per day, so someone who posts across several days counts more than once over the whole window. The figure can overstate breadth, never understate it.

Where it is being said
github99%
hackernews1%
producthunt1%

A wave of praise on a forum and a rapidly filling issue tracker both show up as “mentions up” until you see where they came from.

Agreement
Aligned
spread 0.48 · sides 15% even

Most opinion points the same way, so the average sentiment reads as a verdict rather than two sides cancelling out.

SRC: 376 mentions in window · net sentiment 0.35 · 4 adoption series · derived aggregates only

Mentions / dayall sources combined
02-2505-1708-12
latest 77 mentions02-25 .. 08-12
Sentiment curve0.35 current
02-2505-1608-12
latest 0.3502-25 .. 08-12
GitHub releases / dayadoption
07-2107-2708-07
latest 107-21 .. 08-07
GitHub stars (total)adoption
07-2308-0208-12
latest 47.6k07-23 .. 08-12
npm downloads / dayadoption
06-2207-1608-09
latest 1.6M06-22 .. 08-09
Stack Overflow questions / dayadoption
06-2707-2207-25
latest 106-27 .. 07-25
What people are asking forlatest 20 entries
What was saidKindTimesFirst / LastMomentum
Concurrent prisma-next migrate runs collide when executing migrations against the same database.Bug108-12 → 08-12+0%
Prisma native enum arrays fail to decode with a TypeError when returning from PostgreSQL queries.Bug108-12 → 08-12+0%
A single transient SQLITE_BUSY during COMMIT permanently poisons the whole process and silently loses acknowledged writes in better-sqlite3 adapter.Bug108-09 → 08-09+0%
The orderBy() method accepts a nulls option that is silently discarded and never reaches the SQL query.Bug108-08 → 08-08+0%
Prisma's db verify command fails against current Supabase projects because the extension contract declares storage.iceberg tables that no longer exist in hosted projects.Bug108-05 → 08-05−100%
Prisma's @prisma/adapter-pg does not support custom pg-compatible pool implementations like YugabyteDB's smart driver because it validates against a specific bundled pg.Pool class.Pain point108-05 → 08-05−100%
AddErrorLog function fails with a wasm module evaluation error when using Prisma adapter with Cloudflare runtime.Bug108-04 → 08-04−100%
SQLite concurrent interactive transactions deadlock the query engine when the number of concurrent transactions exceeds worker thread count.Bug108-03 → 08-03−100%
A previous fix for Prisma module format compatibility stopped working, requiring moduleFormat = "cjs" in schema.prisma.Bug108-02 → 08-02−100%
BLOB values from columns with no declared type throw UnexpectedTypeError in the better-sqlite3 adapter.Bug108-02 → 08-02−100%
Query compiler generates invalid SQL for nested upserts on to-one relations with optional where filters.Bug108-02 → 08-02−100%
Raw SQL is required for a basic database operation that should be available in the library, similar to Django ORM.Pain point107-30 → 07-30−100%
The parseJsonFromStderr function unconditionally drops the first line of stderr, causing error information to be lost when only a single line is emitted.Bug107-30 → 07-30−100%
Completion files import from internal src/cli/completion-values path instead of public @prisma/internals entry point.Bug107-29 → 07-29−100%
E2E test consistently fails with changes in nextjs-schema-not-found monorepo-serverComponents-customOutput-noReExport.Bug107-28 → 07-28−100%
prisma.model.upsert() with an empty update object compiles to a non-atomic read-then-write instead of an atomic ON CONFLICT statement, allowing race conditions.Bug107-27 → 07-27−100%
Pool health checks exist in Quaint but cannot be enabled from a connection string, leaving long-running deployments exposed to intermittent connection errors.Pain point107-27 → 07-27−100%
Prisma emits a deprecation warning when using batch transactions with multiple includes and per-parent take clauses.Bug107-26 → 07-26−100%
Prisma schema validation deterministically panics when a PostgreSQL index field reference uses an unsupported function call.Bug107-26 → 07-26−100%
There is no public way to read runtime metadata from a Prisma client, requiring adapters to rely on private internal properties that are not guaranteed to remain stable.Pain point107-26 → 07-26−100%