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

Posted to derby-commits@db.apache.org by Apache Wiki <wi...@apache.org> on 2006/05/08 09:43:40 UTC

[Db-derby Wiki] Update of "HighValueFixCandidates" by KnutAndersHatlen

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by KnutAndersHatlen:
http://wiki.apache.org/db-derby/HighValueFixCandidates

The comment on the change is:
Removed DERBY-1101 since ResultSet.getHoldability() is a JDBC 4.0 method.

------------------------------------------------------------------------------
  ||[http://issues.apache.org/jira/browse/DERBY-1103 DERBY-1103]|| Change the client driver to allow statements to be garbage-collected once they are not referenced in an application|| Often hit by users who expect garbage collection ||
  ||[http://issues.apache.org/jira/browse/DERBY-1058 DERBY-1058]|| derby fails supporting holdable scrollable resultset: ERROR XSCB8: The btree conglomerate 1,141,037,436,752 is closed.||  ||
  ||[http://issues.apache.org/jira/browse/DERBY-1095 DERBY-1095]|| Closing an embedded connection does not seem to close associated EmbedStatements||  ||
- ||[http://issues.apache.org/jira/browse/DERBY-1101 DERBY-1101]|| ResultSet.getHoldabilty will return incorrect value when the ResultSet is obtained from a procedure call||  ||
  ||[http://issues.apache.org/jira/browse/DERBY-1136 DERBY-1136]|| JDBC driver on rs.getFloat() gives LossOfPrecisionConversionException for float fields containing Float.MAX_VALUE||  ||
  ||[http://issues.apache.org/jira/browse/DERBY-1184 DERBY-1184]|| 'CallableStatement.registerOutParameter(int,int,String)' does nothing in client driver||  ||
  ||[http://issues.apache.org/jira/browse/DERBY-331 DERBY-331]|| create table fails when a constraint defintion follows a column default||