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, 28 Apr 2006 00:39:28 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:

  Listings are by branch as some fixes are not appropriate for the maintenance branches. 
Please add issues to the lists or remove/move them if they do not seem appropriate for the
- == High value 10.1 Branch Bug Fixing Candidates ==
+ == 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-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||
+ ||[http://issues.apache.org/jira/browse/DERBY-1219 DERBY-1219]|| 	jdbcapi/checkDataSource.java
and jdbcapi/checkDataSource30.java hang intermittently with client|| 	||
+ ||[http://issues.apache.org/jira/browse/DERBY-1227 DERBY-1227]|| 	Network Server should
not use the underlying embedded prepared statement when accessing a BrokeredPreparedStatement||
+ ||[http://issues.apache.org/jira/browse/DERBY-728 DERBY-728]|| Unable to create databases
whose name containg Chinese characters through the client driver|| 	||
+ ||[http://issues.apache.org/jira/browse/DERBY-803 DERBY-803]||  derbynet/DerbyNetAutoStart.java
test fails intermittently with org.apache.derby.iapi.services.context.ShutdownException||
+ ||[http://issues.apache.org/jira/browse/DERBY-811 DERBY-811]|| 	Creating trace files in
derbytclient fails when running with a SecurityManager|| 	||
+ ||[http://issues.apache.org/jira/browse/DERBY-939 DERBY-939]|| 	NullPointerException at
ResultSet.close() time for simple query using UNION and INTERSECT|| 	||
+ ||[http://issues.apache.org/jira/browse/DERBY-974 DERBY-974]|| 	ClientDriver can lose some
connection properties||  ||
  == 10.1 Branch Porting Candidates ==
  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-85 DERBY-85]|| NPE when creating a trigger
on a table and default schema doesn't exist.|| Often hit by new users. ||
+ ||[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-1009 DERBY-1009]|| Embedded ResultSet.getStatement()
does not return the Statement object that created it for a connection returned from EmbeddedXADataSource||
+ ||[http://issues.apache.org/jira/browse/DERBY-1055 DERBY-1055]||   Security.AccessControlException
in client under SecurityManager when trying to connect using EUSRIDPWD security mechanism||
+ ||[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||
+ ||[http://issues.apache.org/jira/browse/DERBY-387 DERBY-387]|| SimpleNetworkClientSample.java
network server example has an error which causes it to fail||  ||
+ ||[http://issues.apache.org/jira/browse/DERBY-395 DERBY-395]|| Server-side "trace on" and
"trace off" commands do not appear to be working correctly.||  ||
+ ||[http://issues.apache.org/jira/browse/DERBY-479 DERBY-479]|| Passing the return of a RETURN
NULL ON NULL INPUT function to another function call throws linkage error.||  ||
+ ||[http://issues.apache.org/jira/browse/DERBY-508 DERBY-508]|| Wrong classname in javadoc
for ClientDataSource||  ||
+ ||[http://issues.apache.org/jira/browse/DERBY-544 DERBY-544]|| Admin guide has wrong value
for constant TRACE_RESULT_SET_CALLS||  ||
+ ||[http://issues.apache.org/jira/browse/DERBY-616 DERBY-616]|| create index can fail under
the SecurityManager when trying to access files in the tmp folder of a database||  ||
+ ||[http://issues.apache.org/jira/browse/DERBY-635 DERBY-635]|| Client socket connection
doesn't report real socket exception|| ||
+ ||[http://issues.apache.org/jira/browse/DERBY-648 DERBY-648]|| ij 'show connections' statement
does not work in JSR169||  ||
+ ||[http://issues.apache.org/jira/browse/DERBY-693 DERBY-693]|| Incorrect line number in
the error message when parser throws syntax error in some specific examples||  ||
+ ||[http://issues.apache.org/jira/browse/DERBY-7 DERBY-7]|| Bug in NULLIF Function||  ||
+ ||[http://issues.apache.org/jira/browse/DERBY-709 DERBY-709]|| SecurityException thrown
when passing a relative path name when backing up database||  ||
+ ||[http://issues.apache.org/jira/browse/DERBY-732 DERBY-732]|| ERROR XBCM1: Java linkage
error thrown during load of generated class for query with large number of logical operators
and substitution parameters.||  ||
+ ||[http://issues.apache.org/jira/browse/DERBY-739 DERBY-739]|| Reduce generated code required
to access a parameter's value||  ||
+ ||[http://issues.apache.org/jira/browse/DERBY-795 DERBY-795]|| After calling ResultSet.relative(0)
the cursor loses its position|| ||
  == High Value Trunk Bug Fixing Candidates ==

View raw message