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 <noreply@anthropic.com>
This commit is contained in:
Experiments DB Dev
2026-04-23 14:47:50 -04:00
parent 5c0703c271
commit c0d0b8e6ba
+2 -1
View File
@@ -1,5 +1,6 @@
const router = require('express').Router(); const router = require('express').Router();
const { body } = require('express-validator'); const { body } = require('express-validator');
const { Prisma } = require('@prisma/client');
const prisma = require('../lib/prisma'); const prisma = require('../lib/prisma');
const cache = require('../lib/cache'); const cache = require('../lib/cache');
const auditMiddleware = require('../middleware/auditMiddleware'); const auditMiddleware = require('../middleware/auditMiddleware');
@@ -373,7 +374,7 @@ router.get('/:id/daily-statuses', async (req, res, next) => {
where.date = { gte: d, lt: next }; where.date = { gte: d, lt: next };
} }
if (analysisOnly) { if (analysisOnly) {
where.NOT = { analysis_summary: null }; where.NOT = { analysis_summary: Prisma.DbNull };
} }
const statuses = await prisma.dailyStatus.findMany({ const statuses = await prisma.dailyStatus.findMany({