Craig L Russell wrote:
> NoPutResultSet implements ResultSet. What you're describing would > happen if you used a JDBC 3.0 ResultSet with a version of Derby that > didn't support the JDBC 3.0 methods. But I don't know how that could > happen. While NoPutResultSet does implement ResultSet, it's actually org.apache.derby.iapi.sql.ResultSet and not java.sql.ResultSet. Thus any problem is unlikely to be related to JDBC 2 vs. 3. Dan.
