From c0d0b8e6ba21b2244ef6c894494f706e07d00b06 Mon Sep 17 00:00:00 2001 From: Experiments DB Dev Date: Thu, 23 Apr 2026 14:47:50 -0400 Subject: [PATCH] fix: use Prisma.DbNull to filter non-null Json? field in analysisOnly Prisma 5 rejects JS null as a where-clause value on Json? fields. Use Prisma.DbNull (SQL NULL sentinel) so the NOT filter compiles correctly. Co-Authored-By: Claude Sonnet 4.6 --- backend/src/routes/experiments.js | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/backend/src/routes/experiments.js b/backend/src/routes/experiments.js index 3251884..1db58e1 100644 --- a/backend/src/routes/experiments.js +++ b/backend/src/routes/experiments.js @@ -1,5 +1,6 @@ const router = require('express').Router(); const { body } = require('express-validator'); +const { Prisma } = require('@prisma/client'); const prisma = require('../lib/prisma'); const cache = require('../lib/cache'); const auditMiddleware = require('../middleware/auditMiddleware'); @@ -373,7 +374,7 @@ router.get('/:id/daily-statuses', async (req, res, next) => { where.date = { gte: d, lt: next }; } if (analysisOnly) { - where.NOT = { analysis_summary: null }; + where.NOT = { analysis_summary: Prisma.DbNull }; } const statuses = await prisma.dailyStatus.findMany({