Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: derby-commits@db.apache.org
Date: Mon, 07 Jul 2008 22:03:43 -0000
Message-ID: <20080707220343.15786.25356@eos.apache.org>
Subject: [Db-derby Wiki] Update of "HighValueFixCandidates" by KatheyMarsden

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:
http://wiki.apache.org/db-derby/HighValueFixCandidates

------------------------------------------------------------------------------
   * The amount of user/developer time is wasted by the issue.
  
  == High Value Bug Fixing Candidates (10.3, 10.4, 10.5) ==
+ High value fix candidates are marked by the community by checking the "High Value Fix" category in Jira.
+ See [https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&customfield_12310200=High+Value+Fix&resolution=-1&sorter/field=issuekey&sorter/order=DESC High Value Fix Candidates]
- These are issues that would be great to see fixed for the next release.  For other ideas see the full list of
+ in Jira. These are issues that would be great to see fixed for the next release.  For other ideas see the full list of
  [https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310220 Derby Open Code Bugs],
  [https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310744 Regression Test Failures] and [https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&resolution=-1&customfield_12310090=Regression&sorter/field=issuekey&sorter/order=ASC&sorter/field=updated&sorter/order=DESC&sorter/field=priority&sorter/order=DESC Open Product Regressions]
  
- || JIRA_ISSUE   || STATUS ||  SUMMARY    	|| COMMENTS||
- ||[https://issues.apache.org/jira/browse/DERBY-3650 DERBY-3650]|| Open || Derby + Hibernate JPA 3.2.1 problem on entity with Blob/Clob|| ||
- ||[https://issues.apache.org/jira/browse/DERBY-3645 DERBY-3645]|| Open || Insert into selecting BLOB column twice leads to SQLException: Restore of a serializable or SQLData object of class error selecting from the table|| ||
- ||[https://issues.apache.org/jira/browse/DERBY-3646 DERBY-3646]|| Open || Embedded returns wrong results when selecting a blob column twice and using getBinaryStream()|| ||
- ||[https://issues.apache.org/jira/browse/DERBY-3635 DERBY-3635]|| Open || Cannot build SELECT LIST expressions involving row_number()|| ||
- ||[https://issues.apache.org/jira/browse/DERBY-3634 DERBY-3634]|| Open || Cannot use row_number() in ORDERY BY clause|| ||
- ||[https://issues.apache.org/jira/browse/DERBY-3596 DERBY-3596]|| In progress || Creation of logical connections from a pooled connection causes resource leak on the server|| ||
- ||[https://issues.apache.org/jira/browse/DERBY-3312 DERBY-3312 ]|| Open ||Local Network Server Performance degradation with 10.2 or later || regression in 10.2 further regression in 10.3 with lobs||
- ||[https://issues.apache.org/jira/browse/DERBY-3393 DERBY-3393 ]|| Open || Database corruption when adding sleep() in RAFContainer4.writePage()|| ||
- ||[https://issues.apache.org/jira/browse/DERBY-3390 DERBY-3390 ]|| Open || SQLException thrown from user function kills network connection || ||
- ||[https://issues.apache.org/jira/browse/DERBY-151 DERBY-151 ]|| Open || Thread termination -> XSDG after operation is 'complete'  || Suggested solution with jdk 1.4 ||
- ||[https://issues.apache.org/jira/browse/DERBY-1017 DERBY-1017 ]|| Open || locking issue with a select statement using an order by clause  	 ||  	 ||
- ||[https://issues.apache.org/jira/browse/DERBY-1107 DERBY-1107 ]|| Open || For existing databases JDBC metadata queries do not get updated properly between maintenance versions. 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-1256 DERBY-1256 ]|| Open || Remove usage of non-portable methods in derby code 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-1261 DERBY-1261 ]|| Open || Two triggers on same table cause "ERROR 54038: Maximum depth of nested triggers was exceeded." 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-1433 DERBY-1433 ]|| Open || Client driver does not handle string literals containing "where current of" correctly 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-1528 DERBY-1528 ]|| Open || Preparing "INSERT INTO table SELECT FROM (...)" may cause NullPointerException and subsequent internal errors reported by RawStore module 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-1599 DERBY-1599 ]|| Open || Clob.getSubString() throws NullPointerException when created by updatable result set 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-177 DERBY-177 ]  || Open || Unnecessary waiting within EmbedDatabaseMetaData.getIndexInfo() 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-1831 DERBY-1831 ]|| Open || After a database shutdown, Network Server should invalidate all active connections and an appropriate error message should be thrown at the client while using those connections later. 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-2017 DERBY-2017 ]|| In progress, unassigned || Client driver can insert and commit partial data when a LOB stream throws IOException or does not match the specified length 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-2349 DERBY-2349 ]|| Open || Accessing a BLOB column twice in an INSERT trigger leads to errors in the value on-disk 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-2861 DERBY-2861 ]|| Resolved || Thread safety issue in TableDescriptor 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-2990 DERBY-2990 ]|| Open || ResultSet.getBlob holds locks even with READ_UNCOMMITTED isolation level 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-3083 DERBY-3083 ]|| Open || Network server demands a file called "derbynet.jar" in classpath 	|| Controversial ||
- ||[https://issues.apache.org/jira/browse/DERBY-3115 DERBY-3115 ]|| Open || With embedded driver and autocommit, when closing a connection, updates on updatable result set are lost, unless result set is closed 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-700 DERBY-700 ]  || Open || Derby does not prevent dual boot of database from different classloaders on Linux 	|| 	Difficult. Not considered a blocker for 10.1, 10.2 or 10.3||
- ||[https://issues.apache.org/jira/browse/DERBY-723 DERBY-723 ]  || Open || Escaped JDBC/ODBCC function CHAR(n) incorrect maps to Derby's builtin CHAR() function. 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-728 DERBY-728 ]  || Open || Unable to create databases whose name containg Chinese characters through the client driver 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-2991 DERBY-2991 ]|| Open ||Index split deadlock  	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-1482 DERBY-1482 ]|| Open ||Update triggers on tables with blob columns stream blobs into memory even when the blobs are not referenced/accessed. 	|| 	||
-