@wouterdoeland: can you elaborate please? Does not it work or what?

elizarov: I got an expection about there not being a transaction or something. Unfortunately I have already removed the code and switched to handwritten SQL statements so I don't have the code anymore. But basically, I got an exception when trying to call User.find in a coroutine (

launch(CommonPool)

and in ktor)

Can you reproduce it with some selfcontained code and share it?

Wait a minute... Do your transactions have to be in a transaction block? If so then sorry, my fault.

Try #exposed to talk to devs, but I suspect it is not coroutines-ready, because it stores transactions in Thread Local, and coroutine continuation can be scheduled to any thread on a pool. What’s worse, even if you constrain dispatcher to only dispatch on the same thread, several coroutines can be running on a same thread, so their transactions could be messed up. You might need a special coroutine-enabled TransactionManager in Exposed.