R2DBC connection not released back to the pool

[mozguletz]

Existing implementation of AbstractR2DBCQuery.fetch() and unsafeCount() takes an existing connection from the connection provider and uses it, in case if a connection pool is used, the connections are never closed

return getConnection() .flatMapMany( conn -> { ...});

A way to handle the close connection (returning it to the pool)

return Flux.usingWhen(getConnection(), conn -> { ...}, Connection::close);

Is there a way to close the connection from the connection provider in case if a connection pool is used?

[velo]

@mozguletz uuuups.

My bad.

Are you able to submit a pull request fixing it?

Cheers

[xeounxzxu]

@velo @mozguletz I'll try to fix it.

[velo]

Seems no one is working on this, I'm closing to clear the board. Feel free to reopen after a PR is submitted.