is there a way to only connect a relation if the l...
# orm-helpt
Tyler Clendenin
10/09/2021, 6:52 PMis there a way to only connect a relation if the lookup succeeds? relevant question, if two prisma upserts are happening inside a transaction is there any way to ensure that two of them that have the same connectOrCreate don't both try to run a create (they are both runnign asyncrounously and rounded up with a promise.all)?
r
Ryan
10/11/2021, 6:04 AM@Tyler Clendenin 👋
If two upserts are happening at the same time,
connectOrCreatet
Tyler Clendenin
10/11/2021, 2:07 PMhrm, strange. I was getting a duplicate key error so I prefiltered all the creates and ran them first and then just used connect. that worked.
r
Ryan
10/11/2021, 2:17 PMCould you share a small reproduction if possible?
t
Tyler Clendenin
10/12/2021, 9:33 PMi'll see if i can
Tyler Clendenin
10/12/2021, 10:09 PMTyler Clendenin
10/12/2021, 10:09 PM`Unique constraint failed on the fields: (
nametypeuserIdTyler Clendenin
10/12/2021, 10:17 PMoops, that one didn't have the transaction
Tyler Clendenin
10/12/2021, 10:19 PMand in this case when I wrap it in a transaction it seems to work, though I'm pretty sure in my actual case it still threw the errors
Tyler Clendenin
10/12/2021, 10:20 PMthough I would have expected that each prisma upsert was atomic and inside it's own transaction of some sort
r
Ryan
10/13/2021, 5:32 AMYes it runs inside a transaction. You can see the generated SQL as well. If this is reproducible, I would suggest creating an issue here to see what’s causing this.
t
Tyler Clendenin
10/13/2021, 1:10 PMk, issue created
Tyler Clendenin
10/13/2021, 1:11 PM3 Views