[Feature Request] Rollback Interactive Transaction Without throwing Error.

[rojiwon123]

Problem

now (v5.6.0),
In an interactive transaction, we must throw an error to command a rollback.

This has the following drawback:

• non type-safe
• make code less predicatable
• It requires incidental error handling code.

=> potential risk

Suggested solution

• rollback when inner function return Prisma.Rollback instance.

const prisma = new PrismaClien();
const response: Prisma.users | "NOT_FOUND_USER" | "UNVERIFIED_USER" = await prisma.$transaction(async (tx) => {
         const user: Prisma.users | null = await tx.users.findFirst({ where: { id: 1 } });
         
         Prisma.Rollback(); // it is just instance, so this line does nothing.
         
         if(user === null) return Prisma.Rollback("NOT_FOUND_USER");
         if(!user.verified) return Prisma.Rollback("UNVERIFIED_USER");
         // ... some transaction code...
         return user;
    });

class Rollback<T = undefined>{
  constructor(public readonly result: T){};
}

Alternatives

• commit or rollback based on the result of the endHandler.

const prisma = new PrismaClien();
const endHandler = (result: Prisma.users | "NOT_FOUND_USER" | "UNVERIFIED_USER"): boolean => 
        typeof response !== 'string';
    
const response: Prisma.users | "NOT_FOUND_USER" | "UNVERIFIED_USER" = await prisma.$transaction(async (tx) => {
         const user: Prisma.users | null = await tx.users.findFirst({ where: { id: 1 } });        
         if(user === null) return "NOT_FOUND_USER";
         if(!user.verified) return "UNVERIFIED_USER";
         // ... some transaction code...
         return user;
    }, { endHandler });
};

type EndHandler = <T = undefined>(result:T) => boolean;

Additional context

#15211
#8664 (comment)

[SevInf]

Hi @industriously.
There is already a feature request for this functionality in #15211. I am going to close this as a duplicate, if you have any input, please, comment on the other issue.