Most pool methods for DBI generics check out a connection, perform the operation, and the return the connection to the pool, as described in DBI-wrap.
This page describes the exceptions:
DBI::dbSendQuery()
andDBI::dbSendStatement()
can't work with pool because they return result sets that are bound to a specific connection. Instead useDBI::dbGetQuery()
,DBI::dbExecute()
, orlocalCheckout()
.DBI::dbBegin()
,DBI::dbRollback()
,DBI::dbCommit()
, andDBI::dbWithTransaction()
can't work with pool because transactions are bound to a connection. Instead usepoolWithTransaction()
.DBI::dbDisconnect()
can't work because pool handles disconnection.DBI::dbGetInfo()
returns information about the pool, not the database connection.DBI::dbIsValid()
returns whether or not the entire pool is valid (i.e. not closed).
Usage
# S4 method for Pool
dbSendQuery(conn, statement, ...)
# S4 method for Pool,ANY
dbSendStatement(conn, statement, ...)
# S4 method for Pool
dbDisconnect(conn, ...)
# S4 method for Pool
dbGetInfo(dbObj, ...)
# S4 method for Pool
dbIsValid(dbObj, ...)
# S4 method for Pool
dbBegin(conn, ...)
# S4 method for Pool
dbCommit(conn, ...)
# S4 method for Pool
dbRollback(conn, ...)
# S4 method for Pool
dbWithTransaction(conn, code)
Arguments
- conn, dbObj
A Pool object, as returned from
dbPool()
.- statement, code, ...
See DBI documentation.