deanStealth
PPrisma
•Created by deanStealth on 3/12/2025 in #help-and-questions
unique constraint failed on where column? how is possible?
In production, once in a while our customer gets an error on the backend """
Invalid prisma.trainerProposalXrefDbo.update() invocation:
Unique constraint failed on the fields: (id)"""
on the following code """ const promise1 = txClient.trainerProposalXrefDbo.update({
where: {
id: trainerPropXref.id,
proposal_id: trainerPropXref.proposal_id
},
data: {
stage: TrainerProposalStageEnum.CONFIRMED
}
});"""
How is this even possible? I could undertstand violation of a uniqueness column if in the data block but not the where block. I am not sure the stack trace helps
at qn.handleRequestError (/home/node/app/server/node_modules/@prisma/client/runtime/library.js:121:7315)
at qn.handleAndLogRequestError (/home/node/app/server/node_modules/@prisma/client/runtime/library.js:121:6640)
at qn.request (/home/node/app/server/node_modules/@prisma/client/runtime/library.js:121:6347)
at l (/home/node/app/server/node_modules/@prisma/client/runtime/library.js:130:9616)
at async Promise.all (index 0)
at /home/node/app/server/src/controllers/customer/customerController.ts:987:13
at Proxy._transactionWithCallback (/home/node/app/server/node_modules/@prisma/client/runtime/library.js:130:7983)
at CustomerController.runTransactionToAdd (/home/node/app/server/src/controllers/customer/customerController.ts:868:31)
at CustomerController.confirmBook (/home/node/app/server/src/controllers/customer/customerController.ts:824:25)
at /home/node/app/server/src/controllers/customer/customerApiRouting.ts:123:459 replies
PPrisma
•Created by deanStealth on 2/12/2025 in #help-and-questions
Filter on url in GCP lots and all my prisma SQL dissapears!!!
7 replies
PPrisma
•Created by deanStealth on 1/8/2025 in #help-and-questions
Prisma Promises not transferring context like Promises?
A typical pattern in software is
asyncLocalStorage.run(new Map(), () => {
const store = asyncLocalStorage.getStore();
//Generate our own txId for every request
const requestId = generateShortUUID();
store.set('txId', requestId);
//many other setttings like email if exist, clientId from http header if exist
//call controller next(); } Now, in the controller, and business logic and even libraries, this.log.info("some log") spits out all that same information. this information is captured through Promises. It seems prisma promises breaks that though so all my prisma logs that get logged are missing this info. I cannot tell which SQL queries are running against which requestId or email or client id. I filter in GCP the logs frequently on these things and the SQL logs all dissapear. is something missing from PrismaPromises to transfer the asyncLocalStorage context? how to get prisma logging "SQL log" so the underlying logger which calls asyncLocalStorage.getStore().get("txId") will work and get the txId for that request? (yes, this works with many clients as asyncLocalStorage is isolated to the context of each run).
In scala, the Promise has to propogate the context manually. In java, I have a reference to a CompletableFuture that does something similiar. Any reason this breaks in prisma?
//call controller next(); } Now, in the controller, and business logic and even libraries, this.log.info("some log") spits out all that same information. this information is captured through Promises. It seems prisma promises breaks that though so all my prisma logs that get logged are missing this info. I cannot tell which SQL queries are running against which requestId or email or client id. I filter in GCP the logs frequently on these things and the SQL logs all dissapear. is something missing from PrismaPromises to transfer the asyncLocalStorage context? how to get prisma logging "SQL log" so the underlying logger which calls asyncLocalStorage.getStore().get("txId") will work and get the txId for that request? (yes, this works with many clients as asyncLocalStorage is isolated to the context of each run).
In scala, the Promise has to propogate the context manually. In java, I have a reference to a CompletableFuture that does something similiar. Any reason this breaks in prisma?
13 replies