-
Notifications
You must be signed in to change notification settings - Fork 693
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to perform queries outside a db.transaction{ } block #25
Comments
Implemented SpringTransactionManager class (subclass of spring DataSourceTransactionManager). |
Thanks for adding such support. I tried to update Geospatial Messenger project but I got a blocking error: Please also make sure that |
Fixed: IllegalStateException: "Already value"
What about multiplatform? |
@dragossusi , how is it related to that issue? |
I thought he wants to use @transactional with exposed methods |
Yes, it's possible with |
In geospatial-messenger, I am currently forced to
use db.transaction { }
(see MessageRepository).It would be nice if Exposed could make it possible to support existing transaction management system like the one provided by Spring (see this documentation and DataSourceTransactionManager Javadoc).
Exposed could maybe allow to set the default db to use at
Table
level, delegate the transaction management to any kind of other mechanism and allow to perform queries withTable.foo()
functions without a wrapping them into adb.transaction{ }
block.My goal is to be able, potentially with some extensions, to be able to annotate service functions with
@Transactional
and just rely on our regular JDBC based transaction management (more details here).The text was updated successfully, but these errors were encountered: