Is there a way to re-use an existing Jasync connection with an r2dbc client? Something like: https://kotlinlang.slack.com/archives/C03JF82SDHA/p1673956367718769?thread_ts=1673954851.885979&cid=C03JF82SDHA

R2dbc has it's own pool concept. You can try to use that

How do I use the regular Jasync api for all the old code, and re-use that same connection for r2dbc? I need to gradually migrate to komapper... so I don't think just using r2dbc's pooling would solve the problem?

Doesn't sounds like something simple to implement 🤔

You mean turning the Jasync connection into one supported by R2dbc with the above

ConnectionFactory

is not currently possible?

But hiw do you return the connection to the pool

Maybe by not creating a pool with jasync, and letting r2dbc do that with it's pool implementation?

The jasync r2dbc is without pooling. R2dbc pool is separate and use it. If you can get the r2dbc pool instance and get the connection from it you can work on it maybe.

I guess it would be impractical to use the old code w/o a pool anyways... thanks for the suggestions though!

If you end up with a solution let me know. I don't know if the price of two pools during transition is high price to pay