Repository navigation
Replies: 2 comments 2 replies
|
Hey @Shonke! Just to confirm, you want to get the transaction Id when you have enabled logging at Prisma level, like this: const prisma = new PrismaClient({ adapter, log:['query'] });Not like the solution mentioned here? |
2 replies
|
Hi, As we have not heard back from you, we are closing this discussion to keep our discussions organized. Feel free to start a new discussion if this remains relevant. Thank you for being part of the community! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Question
Can it be obtained, or do we need to submit a feature request?
Similar issues are here #17959
But I hope to retrieve them from the query log (which is something else, inside Prisma rather than from the database)
Track in debug:

How to reproduce (optional)
No response
Expected behavior (optional)
No response
Information about Prisma Schema, Client Queries and Environment (optional)
output
prisma : 7.0.1
@prisma/client : 6.19.0
Operating System : darwin
Architecture : arm64
Node.js : v20.19.5
TypeScript : 5.6.3
Query Compiler : enabled
PSL : @prisma/prisma-schema-wasm 7.1.0-2.f09f2815f091dbba658cdcd2264306d88bb5bda6
Schema Engine : schema-engine-cli f09f2815f091dbba658cdcd2264306d88bb5bda6 (at node_modules/@prisma/engines/schema-engine-darwin-arm64)
Default Engines Hash : f09f2815f091dbba658cdcd2264306d88bb5bda6
Studio : 0.8.2
All reactions