commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 12733] New: - [DBCP][PATCH]Statement.getResultSet() doesn't return null if like javadocs
Date Tue, 17 Sep 2002 11:56:13 GMT
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=12733>.
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=12733

[DBCP][PATCH]Statement.getResultSet() doesn't return null if like javadocs

           Summary: [DBCP][PATCH]Statement.getResultSet() doesn't return
                    null if like javadocs
           Product: Commons
           Version: Nightly Builds
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Dbcp
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: funkman@joedog.org


getResultSet() for java.sql.Statement():
the current result as a ResultSet object; null if the result is an update count
or there are no more results

Currently DelegatingPreparedStatement,DelegatingCallableStatement, and
DelegatingStatement return a DelegatingResultSet where the delegate resultset is
null which will cause a NPE on future operations.

Attached is a patch for the 3 files to check for null from getResultSet() via
cvs diff from the HEAD tag

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


Mime
View raw message