Alternative to Apollo Server 4?
Error saving in database
``Unique constraint failed on the constraint:
UkladanieRole_username_key`
at Vn.handleRequestError (C:\Users\wvn_0\Desktop\GalaxyBOT\bot\node_modules@prisma\client\runtime\library.js:121:7339)
at Vn.handleAndLogRequestError (C:\Users\wvn_0\Desktop\GalaxyBOT\bot\node_modules@prisma\client\runtime\library.js:121:6663)...Can't configure compiled Prisma query engine for FreeBSD
Mocking Prisma with Bun

TypeError: The "payload" argument must be of type object. Received null
[TypeError: The "payload" argument must be of type object. Received null] {
code: 'ERR_INVALID_ARG_TYPE'
}
...
Tips for using Neon + Pulse + tRPC for real-time updates
withPulse()
and everything looks like it is setup correctly. However, new events from Pulse seem to arrive either very late or not arrive at all, regardless if I'm using stream()
or subscribe()
.
Here's my tRPC router:
```
onChanges: protectedProcedure.subscription(async function* ({ ctx }) {...Does Pulse .stream() have built-in reconnect logic?
any RDS proxy support ?
Using DELIMITER function in migration
Prisma + Supabase RLS
auth.uid()
etc?Getting P1012 preview feature not found using fullTextSearchPostgres
prisma migrate reset --force
, I am receving the following error:
```
Prisma schema loaded from prisma/schema
Datasource "db": PostgreSQL database "db", schemas "audit, public" at "localhost:5432"
..."payload" argument must be of type object. Received null
Fluent API doesn't work as expected with client extensions
Prisma Promises not transferring context like Promises?
Pulse on ECS
.stream()
or .subscribe
to any of our models. Hunch is that Pulse is driven by a websocket under the hood, and that the ELB is to blame here. Do you have any recommended configurations for this deployment environment?When using createManyAndReturn, am I guaranteed the results order to be the same as of the input?
The "omit" field type is not generated for Prisma client - v6.2.0
omit
exclusion feature (here: https://www.prisma.io/docs/orm/prisma-client/queries/excluding-fields#excluding-a-field-globally-using-omit), I found what may be a generator bug.
I'm seeing the typescript error of, Object literal may only specify known properties, and 'omit' does not exist in type 'Subset<PrismaClientOptions, PrismaClientOptions>'
when attempting to use
new PrismaClient({ omit: { user: password } })
.
...Issues connecting prisma db to next.js
PrismaModule as globle in neatjs with prisma service and dburl