ManageConnection.has_broken implementation about r2d2 HOT 3 CLOSED

If has_broken returns true, the pool will dispose of the connection. The expected behavior is that has_broken should return true if the connection is determined to be broken to the point where it is very unlikely that it would be usable in the future, and it should determine that quickly - with no network or filesystem IO, for example. The implementation for r2d2-postgres checks to see if there have been any IO errors communicating with the database - if so, the communication stream has desynchronized so any further queries will almost certainly fail.

I'm not sure if there's an equivalent state in SQLite since it's talking directly to the filesystem. It may just make sense for your implementation to return false.

from r2d2.

Ok,
There is only memory status check when calling sqlite3_getautocommit and sqlite3_stmt_busy.
What happens if a transaction is pending when a postgresql connection is returned to the pool ?

BEGIN;
INSERT INTO foo (bar) VALUES (1);
-- connection released

Thanks.

from r2d2.

It will continue to be in a transaction. Transactions are managed through an RAII based API that will statically prevent an active transaction if that API is used. If someone manually executes a BEGIN and forgets the accompanying COMMIT or ROLLBACK, nothing currently checks for that fact.

from r2d2.