Adrien Michaud

In my particular case it was asgiref==3.3.1 the culprit, i did a rollback to 3.2.10 and it works well ! I have daphne 2.5.0/channels 2.4.0/django 3.0.10/djangorestframework 3.11.1

Some of us use proxies, so in theory it could be faster. I've tried patching the session.get and session.post and it works well for retrieving statistics of users. You can...

I'm using the last version: 2.1.0 What makes me think that is that we have a strange issue that I documented here: https://github.com/prisma/prisma/discussions/23200 And once I change a portion of...

Here you go: https://github.com/MrVhek/PrismaKyselyBug If you uncomment the working version you'll have the strange issue of a foreign not being found in the same transaction.

I maybe got an idea of what the problem could be. Is it possible that in case I have two transactions in parrallel, the wrong client is used for making...

After investigation, I can definitely reproduce this issue with a simple example: here two kysely get that I parametrized with parameters I know. I've added a function to get an...

I ended up doing my functions and not using this prisma-extension-kysely at all for this You can do ``` const query = tx.$kysely...compile() tx.$queryRawUnsafe(query.sql, ...query.parameters) ```

This is most probably a kysely and/or prisma issue. The way of handling types differ between prisma and kysely, which is why you may need to do some cast.

This looks like a prisma-kysely or kysely issue.