Interactive Transaction GA

[matthewmueller]

This epic is about getting Interactive Transactions out of preview.

Tasks

• Interactive Transaction concurrent writes cause Prisma to hang #11750
• Disable interactive transactions when using the Data Proxy #11913
• Interactive transactions are not logging DB queries #12145
• Close Preview feature feedback: interactiveTransactions #8664
• Some errors are obfuscated by interactive transactions when using binary engine #12862
• Interactive Transactions: fatal when throwing string instead of Error() since 3.10.0 #12663

To reproduce

• High permanent CPU usage after calling $disconnect on a client that executed an interactive transaction before (v3.9.0+) #12516
• Calling the "main" prisma client within an interactive transaction can lead to errors at high concurrency #12277

Discussion needed

• Unexpected 3 retries when using prisma.$transaction after a KnownError in 2.17 and bad error parsing #6156

Nice to have

• Calling the "main" prisma client within an interactive transaction can lead to errors at high concurrency #12277

We should also look to see if any other issues popped up as we were stabilizing this feature.

[DamianGlowala]

Two other issues worth looking at for the GA release:
#11511
#10880

[iddan]

Hey, is there a plan for when interactive transactions will be safe to use in production? The product I'm currently working on can really benefit from it.

[apalumbo]

Hi @garrensmith @millsp thank you for your contribution and your work. As i see both are assignees of the issue I would like to ask you if there is an estimation on when this feature will exit the preview.

[janpio]

That will still take some time. But if you are using Prisma Client without our Data Proxy, you can consider the current state pretty stable - there are no known, reproducible bugs any more - so we will most probably be able to ship the current state GA some time later when the Data Proxy part is covered as well - maybe that let's you move forward already in your usecase.