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).
Re:Prisma Raises $12M Series A
by lukeholder on Friday June 26, 2020 @12:06PM
(#23653538)
Before I could consider Prisma, it would need to support full transactions: https://github.com/prisma/prisma/issues/1844
Re:Prisma Raises $12M Series A
by lukeholder on Friday June 26, 2020 @12:03PM
(#23653498)
How could I write any serious ecommerce/financial product with Prisma without transactions? Thats is crazy. Sticking with Postgres and plain ol' SQL!
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.
Re:Prisma Raises $12M Series A
by hn_reddit_human on Friday June 26, 2020 @01:53PM
(#23654880)
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?
Re:Prisma Raises $12M Series A
by hervelabas on Saturday June 27, 2020 @10:58AM
(#23662219)
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.
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