Allow to perform queries outside a db.transaction{ } block

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 with Table.foo() functions without a wrapping them into a db.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).

[Tapac]

Yes, it’s possible with spring-transaction or exposed-spring-boot modules.

[dragossusi]

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).

I thought he wants to use @Transactional with exposed methods