If reuse is true in the connection pool, existing connections can be reused. But there doesn't seem to be any reset behaviour of such a connection.
If for example on a connection someone issues a specific setting (for example in SQLServer you can set a session specific context) and this connection is afterwards used by another the session specific context still might be set.
Shouldn't the pool have a function to "return a connection to the pool, without destroying it and upon return for reuse it resets"?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
If reuse is true in the connection pool, existing connections can be reused. But there doesn't seem to be any reset behaviour of such a connection.
If for example on a connection someone issues a specific setting (for example in SQLServer you can set a session specific context) and this connection is afterwards used by another the session specific context still might be set.
Shouldn't the pool have a function to "return a connection to the pool, without destroying it and upon return for reuse it resets"?