Go through the existing iTX and explore what needs to be worked on

[millsp]

This involves:

• Looking at existing issues
• Evaluating their severity
• Eventually get a repro working
• Plan what should be tackled

[millsp]

New feature for later:

• Interactive transactions: Allow setting isolation level #8668

Worth taking a look / Needed:

• Interactive transaction: Sequential Prisma Client operations timeout but work when interactive transactions are disabled #11654
• groupBy is not usable with $transaction #7918
• InteractiveTransaction: Middleware param runInTransaction set to false #9073
• interactiveTransactions feature breaks long running transactions #11565
• Using "then ()" in "interactive Transactions" initiates another transaction #10615
• prisma instance from transaction does not inherit config #10886
• Error when looking up interactive transaction feature flag (Nestjs) #11036

Nice to have:

• Expose the type that is passed to the interactive $transaction function #11511
• Middlewares to include transaction and for it to have an afterCommit hook #9083

Can probably be closed:

• Prisma interactive transactions API error: "Argument of type 'x' is not assignable to parameter of type 'PrismaPromise<any>[]'" #8739
• $transaction performance issue within Docker #9846
• Interactive transaction is not rolling back if it's interrupted in the middle by "throw Error" #11107

Unknown:

• Issue with prisma 2.29.0 the engine errors with Transaction API error: Unable to start a transaction in the given time #8708

[garrensmith]

Required:

• groupBy is not usable with $transaction #7918
• Unexpected 3 retries when using prisma.$transaction after a KnownError in 2.17 and bad error parsing #6156

Unknown:

• Suggestion: using AsyncLocalStorage for transactions #5729