New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wrong error message/header on multiple table upsert using transaction #15433
Labels
bug/1-unconfirmed
Bug should have enough information for reproduction, but confirmation has not happened yet.
kind/bug
A reported bug.
team/client
Issue for team Client.
topic: transaction
topic: upsert
nested upsert
Milestone
Comments
@hitzam-wartek could you share your schema and the query you are doing? A reproduction would also help us here. |
Hi @garrensmith, here's the schema & query
|
millsp
added
team/client
Issue for team Client.
bug/1-unconfirmed
Bug should have enough information for reproduction, but confirmation has not happened yet.
bug/0-unknown
Bug is new, does not have information for reproduction or reproduction could not be confirmed.
and removed
bug/1-unconfirmed
Bug should have enough information for reproduction, but confirmation has not happened yet.
labels
Sep 21, 2022
janpio
removed
the
bug/0-unknown
Bug is new, does not have information for reproduction or reproduction could not be confirmed.
label
Sep 22, 2022
millsp
added a commit
that referenced
this issue
Oct 20, 2022
SevInf
added a commit
to prisma/prisma-engines
that referenced
this issue
Nov 11, 2022
Adds `batch_request_idx` property to user facing errors. On the client, that would allow us to build correct error message for `$transaction` errors. Ref: prisma/prisma#15433, prisma/prisma#14373
SevInf
added a commit
to prisma/prisma-engines
that referenced
this issue
Nov 11, 2022
Adds `batch_request_idx` property to user facing errors. On the client, that would allow us to build correct error message for `$transaction` errors. Ref: prisma/prisma#15433, prisma/prisma#14373
SevInf
added a commit
that referenced
this issue
Nov 11, 2022
Engine PR: prisma/prisma-engines#3384 Uses newly added `batch_request_idx` property of an errors to identify and correctly report error location within a batch. Fix #15433 Fix #14373
SevInf
added a commit
to prisma/prisma-engines
that referenced
this issue
Nov 11, 2022
Adds `batch_request_idx` property to user facing errors. On the client, that would allow us to build correct error message for `$transaction` errors. Ref: prisma/prisma#15433, prisma/prisma#14373
SevInf
added a commit
that referenced
this issue
Nov 11, 2022
Engine PR: prisma/prisma-engines#3384 Uses newly added `batch_request_idx` property of an errors to identify and correctly report error location within a batch. Fix #15433 Fix #14373
SevInf
added a commit
that referenced
this issue
Nov 11, 2022
Engine PR: prisma/prisma-engines#3384 Uses newly added `batch_request_idx` property of an errors to identify and correctly report error location within a batch. Fix #15433 Fix #14373
SevInf
added a commit
that referenced
this issue
Nov 14, 2022
Engine PR: prisma/prisma-engines#3384 Uses newly added `batch_request_idx` property of an errors to identify and correctly report error location within a batch. Fix #15433 Fix #14373
SevInf
added a commit
to prisma/prisma-engines
that referenced
this issue
Nov 15, 2022
* qe: Identify which request in a batch caused error Adds `batch_request_idx` property to user facing errors. On the client, that would allow us to build correct error message for `$transaction` errors. Ref: prisma/prisma#15433, prisma/prisma#14373
SevInf
added a commit
that referenced
this issue
Nov 15, 2022
Engine PR: prisma/prisma-engines#3384 Uses newly added `batch_request_idx` property of an errors to identify and correctly report error location within a batch. Fix #15433 Fix #14373
SevInf
added a commit
that referenced
this issue
Nov 15, 2022
Engine PR: prisma/prisma-engines#3384 Uses newly added `batch_request_idx` property of an errors to identify and correctly report error location within a batch. Fix #15433 Fix #14373
SevInf
added a commit
that referenced
this issue
Nov 16, 2022
Engine PR: prisma/prisma-engines#3384 Uses newly added `batch_request_idx` property of an errors to identify and correctly report error location within a batch. Fix #15433 Fix #14373
SevInf
added a commit
that referenced
this issue
Nov 16, 2022
Engine PR: prisma/prisma-engines#3384 Uses newly added `batch_request_idx` property of an errors to identify and correctly report error location within a batch. Fix #15433 Fix #14373
SevInf
added a commit
that referenced
this issue
Nov 17, 2022
Engine PR: prisma/prisma-engines#3384 Uses newly added `batch_request_idx` property of an errors to identify and correctly report error location within a batch. Fix #15433 Fix #14373
SevInf
added a commit
that referenced
this issue
Nov 17, 2022
…6240) Engine PR: prisma/prisma-engines#3384 Uses newly added `batch_request_idx` property of an errors to identify and correctly report error location within a batch. Fix #15433 Fix #14373
jkomyno
pushed a commit
that referenced
this issue
Dec 21, 2022
…6240) Engine PR: prisma/prisma-engines#3384 Uses newly added `batch_request_idx` property of an errors to identify and correctly report error location within a batch. Fix #15433 Fix #14373
jkomyno
pushed a commit
that referenced
this issue
Dec 21, 2022
…6240) Engine PR: prisma/prisma-engines#3384 Uses newly added `batch_request_idx` property of an errors to identify and correctly report error location within a batch. Fix #15433 Fix #14373
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug/1-unconfirmed
Bug should have enough information for reproduction, but confirmation has not happened yet.
kind/bug
A reported bug.
team/client
Issue for team Client.
topic: transaction
topic: upsert
nested upsert
Bug description
Hi Prisma team,
So, I have 3 tables that need to upsert at once using transaction, and I need to log the exception when something wrong on execution.
I tried to make the execution failed by putting some invalid data of first table. and it worked well, I got the error message & the error detail correctly, something like
Error: Invalid
prisma.table_1.upsert()invocation: --detail error message that related to table 1--
.on second attempt, I put invalid data on the second table, and it's not worked as expected, the error message/header still referring to first table while the error detail relates to second table.
Error: Invalid
prisma.table_1.upsert()invocation: --detail error message that related to table 2--
.it also happen when something is wrong on the 3rd table, the error header still refering to 1st table.
How to reproduce
Expected behavior
expected behavior: error message/header should refer to the table where the error comes.
Error: Invalid
prisma.table_1.upsert()invocation: --detail error message that related to table 1--
.Error: Invalid
prisma.table_2.upsert()invocation: --detail error message that related to table 2--
.Error: Invalid
prisma.table_3.upsert()invocation: --detail error message that related to table 3--
.Prisma information
// Add your schema.prisma
// Add your code using Prisma Client
Environment & setup
Prisma Version
The text was updated successfully, but these errors were encountered: