Which means that we can either bind the client.$transactions to each model so we can call it from the function without having to frakenstein it into each function. Technically this would create a callable function on the user-facing API. But it might be justifiable.
Implementing this would also remove the need to mention SQLite connection_limit. At least in the limited testing I've done, that seem to have been solved by it.
According to the latest documentation on prisma extension you can use $transactions like this: https://www.prisma.io/docs/concepts/components/prisma-client/client-extensions/shared-extensions#call-a-client-level-method-from-your-packaged-extension
Which means that we can either bind the
client.$transactions
to each model so we can call it from the function without having to frakenstein it into each function. Technically this would create a callable function on the user-facing API. But it might be justifiable.