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, 05 May 2006 21:11:45 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:

  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-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 ==
- These are major fixes that are important to users but not appropriate for the maintenance
+ These are major fixes that are important to users but may not appropriate for the maintenance
branch. Of course once fixed, they can be evaluated and maybe port to 10.1 will be fine.
  || JIRA_ISSUE   ||  SUMMARY    	|| COMMENTS ||
+ ||[http://issues.apache.org/jira/browse/DERBY-550  DERBY-550]||BLOB : java.lang.OutOfMemoryError
with network JDBC driver with setBinaryStream || Client always materializes the LOB, even
when using setBinaryStream.  This is the client side equivalent of [http://issues.apache.org/jira/browse/DERBY-326
DERBY-326] ||
+ || [http://issues.apache.org/jira/browse/DERBY-700  DERBY-700]   || Derby does not prevent
dual boot of database from different classloaders on Linux || Dual boot and corruption of
the db should never be allowed and more and more users are using custom class loaders. This
is being reported more and more ||
+ || [http://issues.apache.org/jira/browse/DERBY-634 DERBY-634 ]   ||  Subquery materialization
can cause stack overflow || Reported by users and has potential to become a frequently hit
scalability issue for DERBY queries ||
+ || [http://issues.apache.org/jira/browse/DERBY-176  DERBY-176] ||  Derby throws ERROR XBCM1:
Java linkage error thrown during load of generated class during execution of large query ||
 This is an issue usually when users write large queries with repeat constructs. The problem
is that there is no clear upper bound that can be documented, so often users deploy applications
that generate large queries that may not fail in testing but do once deployed. The solution
is usually a combination of the user trying to reduce the query size and code generation optimizations.
Both  are hard to do in a crisis.   One example of this is users that work around the  absence
of recursive queries http://issues.apache.org/jira/browse/DERBY-267 DERBY-267]  by using generated
queries with lots of unions. In this case, there is no user workaround if the results are
large enough ||

View raw message