[hn_reddit_human]

I mentioned this the last time, but I find it surprising that the Prisma ORM doesn't support transactions or aggregations?

Any thoughts from the Prisma team? It kind of seems like table stakes. I commented on this previously as well: https://news.ycombinator.com/item?id=23467427

[Sujan]

This time I can answer that some aggregations are in the current milestone: https://github.com/prisma/prisma/issues/2838 That could mean they will be available very soon. (If you are missing any other ones, please comment on that issue or create a new one!)

Transactions were actually included in the last release https://github.com/prisma/prisma/releases/tag/2.1.0 (search for `transactionApi`) in a specific form behind a feature flag (batch transactions, not long running transactions).

[lukeholder]

Before I could consider Prisma, it would need to support full transactions: https://github.com/prisma/prisma/issues/1844

[lukeholder]

How could I write any serious ecommerce/financial product with Prisma without transactions? Thats is crazy. Sticking with Postgres and plain ol' SQL!

[sorenbs]

Prisma supports transactions through the `prisma.transaction` API. This allow you to perform multiple DB actions in a single request and gives you an all-or-nothing semantic.

[hn_reddit_human]

Thanks!

IIUC, a "batch" request is run in a transaction.But if I need to run business logic in the middle of requests that's not supported?

[hervelabas]

Not yet indeed. Prisma doesn't support long running transactions and advocates for alternative ways. We're preparing a post on the topic soon, and will improve the means for those alternatives.