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/13 10:50:29 UTC

DO NOT REPLY [Bug 24678] New: - DelegatingStatement.getResultSet() never returns null

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=24678>.
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=24678

DelegatingStatement.getResultSet() never returns null

           Summary: DelegatingStatement.getResultSet() never returns null
           Product: Commons
           Version: 1.1 Final
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Dbcp
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: r_jacobs@gmx.de


The API documentation of java.sql.Statement.getResultSet() states: "Returns: 
[...] null if the result is an update count or there are no more results"

getResultSet() of DelegatingStatement always returns an instance of 
DelegatingResultSet even if the delegate's ResultSet is null.
GetResultSet() should return null, if the delegate's ResultSet is null.

The same applies to DelegatingPreparedStatement.

Now to the good news: DelegatingCallableStatement.getResultSet() handles this 
case correctly by calling DelegatingResultSet.wrapResultSet(). This method 
checks the delegate's ResultSet.

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