prisma/prisma-engines - CodSpeed

prisma-engines

Blog Docs Changelog

Performance History

Latest Results

chore: [integration] minor changes

feat/minor-fixes-on-qc-parameterization

7 days ago

fix(qc): don't panic on placeholders in full text search `matches`/`not_matches` operations needed to be adjusted to accept placeholders. The corresponding fields in DMMF were already marked as parameterizable so QC panicked in Client tests here.

aqrln-nnwpqtmklwqq

7 days ago

feat(qc): implement placeholder validation

aqrln-uvzslzzyztys

7 days ago

fix(qc): don't panic on placeholders in full text search `matches`/`not_matches` operations needed to be adjusted to accept placeholders. The corresponding fields in DMMF were already marked as parameterizable so QC panicked in Client tests here.

aqrln-nnwpqtmklwqq

8 days ago

fix(qc): don't panic on placeholders in full text search `matches`/`not_matches` operations needed to be adjusted to accept placeholders. The corresponding fields in DMMF were already marked as parameterizable so QC panicked in Client tests here.

aqrln-nnwpqtmklwqq

8 days ago

feat(qc): implement placeholder validation

aqrln-uvzslzzyztys

8 days ago

fix(qc): don't panic on placeholders in full text search `matches`/`not_matches` operations needed to be adjusted to accept placeholders. The corresponding fields in DMMF were already marked as parameterizable so QC panicked in Client tests here.

aqrln-nnwpqtmklwqq

8 days ago

fix(quaint): cast BigInt to text in JSON aggregation (#5745) ## Problem When using `relationJoins` with BigInt fields in Prisma 7, JavaScript's `JSON.parse` loses precision for integers larger than `Number.MAX_SAFE_INTEGER` (2^53 - 1). This happens because PostgreSQL's `JSONB_BUILD_OBJECT` returns BigInt values as JSON numbers, which JavaScript cannot represent precisely. Example: ``` // Original BigInt ID: 312590077454712834 // After JSON.parse: 312590077454712830 (corrupted!) ``` ## Solution Cast BigInt columns to `::text` inside `JSONB_BUILD_OBJECT` calls, similar to how MONEY is already cast to `::numeric`. ```sql -- Before JSONB_BUILD_OBJECT('id', "id") -- After JSONB_BUILD_OBJECT('id', "id"::text) ``` This ensures BigInt values are returned as JSON strings, preserving full precision when parsed in JavaScript. ## Changes - Added BigInt → `::text` cast in `visit_json_build_obj_expr` (quaint/src/visitor/postgres.rs) - Added test case for BigInt casting ## Related - prisma/prisma#29009 (TypeScript-level workaround in prisma fork) ## Test plan - [x] Added unit test for BigInt casting in `test_json_build_object` - [ ] CI tests pass --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

main

8 days ago

Active Branches

chore: minor fixes on qc parameterization

last run

7 days ago

0%

fix(qc): don't panic on placeholders in full text search

last run

7 days ago

0%

feat(qc): implement placeholder validation

last run

7 days ago

0%

© 2026 CodSpeed Technology

Home Terms Privacy Docs