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, 13 Apr 2007 23:30: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:

   * Availability of a workaround.
   * The amount of user/developer time is wasted by the issue.
- 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.3 Bug Fixing Candidates ==
+ This are issues that would be great to see fixed for the release.
+ ||[http://issues.apache.org/jira/browse/DERBY-2370 DERBY-2370]||EXISTS may return the wrong
value  ||
+ ||[http://issues.apache.org/jira/browse/DERBY-889 DERBY-889]|| 	with client getTimestamp
on a TIME column will print the date 1900-01-01 instead of the current date||  ||
+ ||[http://issues.apache.org/jira/browse/DERBY-1030 DERBY-1030]|| In some situations a RETURNS
NULL ON NULL function is called when one ot its parameters is NULL|| ||
+ ||[http://issues.apache.org/jira/browse/DERBY-2017 DERBY-2017]||Client driver can insert
and commit partial data when a LOB stream throws IOException or does not match the specified
length || ||
+ ||[http://issues.apache.org/jira/browse/DERBY-1816 DERBY-1816]||Client's ResultSet.getTime()
on a SQL TIMESTAMP column loses the sub-second resolution and always has a milli-second value
of zero.|| ||
+ ||[http://issues.apache.org/jira/browse/DERBY-2381 DERBY-2381]||ParameterMappingTest fails
due to ArrayIndexOutOfBoundsException || ||
+ ||[http://issues.apache.org/jira/browse/DERBY-2459 DERBY-2459]||Ordering on a CASE-expression
casues a NullPointerException when using a UNION || ||
+ ||[http://issues.apache.org/jira/browse/DERBY-2352 DERBY-2352]|| Assertion Failure with
order by and group by expression || ||
+ ||[http://issues.apache.org/jira/browse/DERBY-2351 DERBY-2351]||ORDER BY with expression
with distinct in the select list returns incorrect result || ||
+ ||[http://issues.apache.org/jira/browse/DERBY-1782 DERBY-1782]||When a privilege is revoked
at table level, Derby should only drop objects that require that particular privilege|| ||
+ ||[http://issues.apache.org/jira/browse/DERBY-1465 DERBY-1465]|| NetworkServerControl.start()
should throw an exception and not just print exceptions if the server fails to start|| ||
+ ||[http://issues.apache.org/jira/browse/DERBY-1256 DERBY-1256]||Remove usage of non-portable
methods in derby code || ||
+ ||[http://issues.apache.org/jira/browse/DERBY-1025 DERBY-1025]||[xa] client XAResource.start()
does not commit an active local transaction when auto commit is true || ||
+ ||[http://issues.apache.org/jira/browse/DERBY-857 DERBY-857]||LDAP user authentication fails
under a security manager|| ||
+ ||[http://issues.apache.org/jira/browse/DERBY-974 DERBY-974]||ClientDriver can lose some
connection properties || ||
+ ||[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-588 DERBY-588]||database created on zOS (os/390)
cannot be used on windows || ||
+ ||[http://issues.apache.org/jira/browse/DERBY-341 DERBY-341]|| Client should disallow XAConnection
getConnection() when a global transaction has been started and a logical connection has already
been obtained|| ||
+ ||[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-811 DERBY-811]||Creating trace files in derbytclient
fails when running with a SecurityManager || ||
- == 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.
- ||[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-1183 DERBY-1183]|| 	Client java.sql.ResultSet.getCursorName()
does not return the correct cursor name for Statements after the first execution|| The user
cannot even workaround this issue by calling setCursorName() again. May be low hanging fruit||
- ||[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-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-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||  ||
- ||[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-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-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-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||  ||
- == High Value Trunk Bug Fixing Candidates ==
- 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-47  DERBY-47]|| IN Optimization issues ||This
issue and its clone  [http://issues.apache.org/jira/browse/DERBY-713 DERBY-713] represent
10 votes in Jira and it make it by far the most popular issue.  The performance impact of
this issue on many users is significant enough for them to file it a bug although we have
it filed as an improvement||
- ||[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