Any technical reason for mandatory transaction scope
Open
- Dominant language
- Kotlin
- Stars
- 9.3k
- Forks
- 798
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 26
Description
Hello,
I am curious why Exposed requires to make any SQL action in a transaction scope, why such overhead is always needed?
I didn't find the answer in Wiki or Google. I understand why Hibernate requires transactions with its PersistanceContext and dirty checking, but why I should open a transaction in Exposed every time when I need just to read the table is not clear for me.
For example, other framework TypeORM (from nodejs world) doesn't have such limitations and the user (programmer) can read and even insert & modify data without transactions.
Contributor guide
Assessment
This issue has not been assessed yet.