v3.0.0

What's changed

• Arrays of enums are Prisma's to read, from @prisma/orm-postgres 8.0.0-rc.12. dataPool() used to parse an array of enums into a JavaScript array before the runtime saw it, because up to 8.0.0-rc.11 the runtime could not read the raw text node-postgres gives for a type it cannot number in advance. From 8.0.0-rc.12 the runtime decodes every array from that raw text itself and refuses one already parsed, so every read of such a column failed with RUNTIME.DECODE_FAILED: "expected raw text for a Postgres array, got object". The enum lookup is gone, and with it the deferred first-connection hook that existed only to run it. The json[] and jsonb[] parsers are dropped too; json and jsonb are still left as text for the codec's one parse.

Breaking: the @prisma/orm-postgres peer dependency is now >=8.0.0-rc.12, and TypeParsers asks only for setTypeParser.

Full Changelog: v2.4.0...v3.0.0

About

@imqueue/pg-prisma — Prisma Next (8.x) / Postgres toolkit for Node.js & TypeScript microservices — query middlewares (soft-delete, authorship, audit, access-scope) derived from the emitted contract, row archiving and change-notify triggers. Part of the @imqueue framework for Node.js & TypeScript microservices.

• Docs: https://imqueue.org/
• Guide for AI assistants / LLMs: https://imqueue.org/llms.txt
• Commercial license & support: https://imqueue.com/
• npm i @imqueue/pg-prisma