Skip to content
This repository has been archived by the owner on Jan 14, 2021. It is now read-only.

Long running transactions #742

Closed
timsuchanek opened this issue Jun 23, 2020 · 1 comment
Closed

Long running transactions #742

timsuchanek opened this issue Jun 23, 2020 · 1 comment
Labels
kind/discussion Discussion is required.

Comments

@timsuchanek
Copy link
Contributor

With #667 being implemented in 2.1.0, we now support transactions, which batch queries together, which are directly executed in sequence. If one of the queries (or mutations) fails, all previous ones are rolled back.

While this probably already covers the majority of use-cases, many users mentioned, that they in addition are interested in long-running transactions. Such a long-running transaction would for example allow you to start a transaction, execute code, do another query and then end the transaction.

It has been an explicit design decision by Prisma to not implement those transactions for now.

We will explain in-depth soon, why that is.
Until then, we can use this issue as a discussion platform to discuss the topic.

@timsuchanek
Copy link
Contributor Author

Closing this in favor of prisma/prisma#1844

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/discussion Discussion is required.
Projects
None yet
Development

No branches or pull requests

1 participant