commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Todd Carmichael <>
Subject [dbcp] PooledConnectionImpl.prepareStatement(String, int, int)
Date Sat, 01 Nov 2003 05:37:13 GMT
DBCP Team,
What is the reason that the extended version of prepareStatement in
PooledConnectionImpl that accepts resultSetType and resultSetConcurrency
does not pass those values down to the the real connection object?  I will
pass those values to the connection object IF statement pooling is enabled.
However, if statement pooling is not enabled it does not pass those values:

~ line 257
PreparedStatement prepareStatement(String sql, int resultSetType, int
resultSetConcurrency) throws SQLException {
        if (pstmtPool == null) {
            return connection.prepareStatement(sql);


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message