db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "HighValueFixCandidates" by KatheyMarsden
Date Fri, 26 May 2006 18:33:23 GMT
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 KatheyMarsden:

  == High Value 10.1 Branch Bug Fixing Candidates ==
  These are issues that would be great to see fixed in the maintenance branch. Once fixed
in the trunk, an assessment should be made of whether they are appropriate for port to 10.1.
- || JIRA_ISSUE   ||  SUMMARY    	|| COMMENTS ||
- ||[http://issues.apache.org/jira/browse/DERBY-1002 DERBY-1002]|| 	 Check that DRDAStatement
and DRDAResultSet states are reset when they are re-used|| 	||
+ ||[http://issues.apache.org/jira/browse/DERBY-1069 DERBY-1069]||Client should unwrap exceptions
thrown in privilege blocks. || We could avoid lots of user questions generated by client messages
like: "java.security.PrivilegedActionException : Error opening socket to server xx on port
1527 with message : null". Just not very helpful||
  ||[http://issues.apache.org/jira/browse/DERBY-1004 DERBY-1004]||  Client should not require
user to rollback the active transaction before call to PooledConnection.getConnection()||
  ||[http://issues.apache.org/jira/browse/DERBY-1018 DERBY-1018]||  Client xa Statement.getConnection
and DatabaseMetadata.getConnection returns underlying NetXAConnection instead of Logical connection||
  ||[http://issues.apache.org/jira/browse/DERBY-1020 DERBY-1020]|| 	Network Server treats
errors on cleanup of connections as an unexpected error after intentional shutdown of the
database/server|| 	||
  ||[http://issues.apache.org/jira/browse/DERBY-1107 DERBY-1107]|| 	 For existing databases
JDBC metadata queries do not get updated properly between maintenance versions.|| 	||
- ||[http://issues.apache.org/jira/browse/DERBY-1148 DERBY-1148]|| 	Client XA getTransactionIsolation()
does not return the correct isolation level when rejoining a global transaction|| 	||
  ||[http://issues.apache.org/jira/browse/DERBY-1183 DERBY-1183]|| 	Client java.sql.ResultSet.getCursorName()
does not return the correct cursor name for Statements after the first execution|| 	||
  ||[http://issues.apache.org/jira/browse/DERBY-1191 DERBY-1191]|| 	Some SQLExceptions, for
example those generated from BrokeredStatements, do not print to derby.log even when derby.stream.error.logSeverityLevel=0||
  ||[http://issues.apache.org/jira/browse/DERBY-1204 DERBY-1204]|| 	CREATE TRIGGER with an
INSERT action statement with multiple rows and a referenced column throws a StringIndexOutOfBoundsException||
@@ -39, +38 @@

  Many bugs have been fixed in trunk that would be valuable to users in the maintenance branch.
 They have already been fixed and just need someone to port them to the 10.1 branch where
folks can use them.  Porting fixes made by others is a great way to learn about Derby!
  || JIRA_ISSUE   ||  SUMMARY    	|| COMMENTS ||
- ||[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-1136 DERBY-1136]|| JDBC driver on rs.getFloat()
gives LossOfPrecisionConversionException for float fields containing Float.MAX_VALUE||  ||

View raw message