You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2003/11/02 01:38:22 UTC

DO NOT REPLY [Bug 24328] New: - PooledConnectionImpl ignores resultsetType and Concurrency if statement pooling is not enabled

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24328>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24328

PooledConnectionImpl ignores resultsetType and Concurrency if statement pooling is not enabled

           Summary: PooledConnectionImpl ignores resultsetType and
                    Concurrency if statement pooling is not enabled
           Product: Commons
           Version: 1.1.0
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Dbcp
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: toddc@concur.com


Around line 261 in PooledConnectionImpl, the method preparedStatement fowrards
the request to to the real connection.  However the resultSetType and
Resultsetconcurrency are NOT passed down.
   /**
     * Create or obtain a {*link PreparedStatement} from my pool.
     * @return a {*link PoolablePreparedStatement}
     */
    PreparedStatement prepareStatement(String sql, int resultSetType, 
                                       int resultSetConcurrency) 
            throws SQLException {
        if (pstmtPool == null) {
            return connection.prepareStatement(sql);

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org