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 DyreTjeldvoll
Date Thu, 17 Jan 2008 10:59:01 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 DyreTjeldvoll:
http://wiki.apache.org/db-derby/HighValueFixCandidates

------------------------------------------------------------------------------
  [https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310220
Derby Open Code Bugs] and
  [https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310744
Regression Test Failures.]
  
- || JIRA_ISSUE   ||  SUMMARY    	|| COMMENTS||
+ || JIRA_ISSUE   || Status ||  SUMMARY    	|| COMMENTS||
- ||[https://issues.apache.org/jira/browse/DERBY-3253   	    	 DERBY-3253  	 ]||NullPointer
Exception (NPE) from query with IN predicate containing two values and joining a view with
a large table. ERROR 38000: The exception 'java.lang.NullPointerException' was thrown while
evaluating an expression.  	   	 ||regression in 10.3  	 ||
+ ||[https://issues.apache.org/jira/browse/DERBY-3253   	    	 DERBY-3253  	 ]|| || NullPointer
Exception (NPE) from query with IN predicate containing two values and joining a view with
a large table. ERROR 38000: The exception 'java.lang.NullPointerException' was thrown while
evaluating an expression.  	   	 ||regression in 10.3  	 ||
- ||[https://issues.apache.org/jira/browse/DERBY-3257  	    	 DERBY-3257  	 ]||  	SELECT with
HAVING clause containing OR conditional incorrectly return 1 row - should return 2 rows -
works correctly with 10.2 DB  	 ||regression in 10.3  	 ||
+ ||[https://issues.apache.org/jira/browse/DERBY-3257  	    	 DERBY-3257  	 ]|| ||  	SELECT
with HAVING clause containing OR conditional incorrectly return 1 row - should return 2 rows
- works correctly with 10.2 DB  	 ||regression in 10.3  	 ||
- ||[https://issues.apache.org/jira/browse/DERBY-3230  	    	 DERBY-3230  	 ]||  	 [DERBY-1017]
locking issue with a select statement using an order by clause  	 ||  	 ||
+ ||[https://issues.apache.org/jira/browse/DERBY-3230  	    	 DERBY-3230  	 ]|| ||  	 [DERBY-1017]
locking issue with a select statement using an order by clause  	 ||  	 ||
- ||[https://issues.apache.org/jira/browse/DERBY-3230 DERBY-3230  	 ]||  Selecting data from
a Table raises Error XN008: Query processing has been terminated due to an error on the server
	 ||  	 ||
+ ||[https://issues.apache.org/jira/browse/DERBY-3230 DERBY-3230  	 ]|| ||  Selecting data
from a Table raises Error XN008: Query processing has been terminated due to an error on the
server 	 ||  	 ||
- ||[https://issues.apache.org/jira/browse/DERBY-1107 	  	DERBY-1107 	]|| 	[DERBY-1107] For
existing databases JDBC metadata queries do not get updated properly between maintenance versions.
	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-1107 	  	DERBY-1107 	]|| || 	[DERBY-1107]
For existing databases JDBC metadata queries do not get updated properly between maintenance
versions. 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-1256 	  	DERBY-1256 	]|| 	[DERBY-1256] Remove
usage of non-portable methods in derby code 	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-1256 	  	DERBY-1256 	]|| || 	[DERBY-1256]
Remove usage of non-portable methods in derby code 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-1261 	  	DERBY-1261 	]|| 	[DERBY-1261] Two
triggers on same table cause "ERROR 54038: Maximum depth of nested triggers was exceeded."
	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-1261 	  	DERBY-1261 	]|| || 	[DERBY-1261]
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 	]|| 	[DERBY-1433] Client
driver does not handle string literals containing "where current of" correctly 	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-1433 	  	DERBY-1433 	]|| || 	[DERBY-1433]
Client driver does not handle string literals containing "where current of" correctly 	||
	||
- ||[https://issues.apache.org/jira/browse/DERBY-1528 	  	DERBY-1528 	]|| 	[DERBY-1528] Preparing
"INSERT INTO table SELECT FROM (...)" may cause NullPointerException and subsequent internal
errors reported by RawStore module 	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-1528 	  	DERBY-1528 	]|| || 	[DERBY-1528]
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 	]|| 	[DERBY-1599] Clob.getSubString()
throws NullPointerException when created by updatable result set 	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-1599 	  	DERBY-1599 	]|| || 	[DERBY-1599]
Clob.getSubString() throws NullPointerException when created by updatable result set 	|| 
||
- ||[https://issues.apache.org/jira/browse/DERBY-177 	  	DERBY-177 	]|| 	[DERBY-177] Unnecessary
waiting within EmbedDatabaseMetaData.getIndexInfo() 	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-177 	  	DERBY-177 	]|| || 	[DERBY-177] Unnecessary
waiting within EmbedDatabaseMetaData.getIndexInfo() 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-1781 	  	DERBY-1781 	]|| 	[DERBY-1781] Process
handles appear to be leaking in queries using an IN clause during concurrent DB access 	||
	||
+ ||[https://issues.apache.org/jira/browse/DERBY-1781 	  	DERBY-1781 	]|| || 	[DERBY-1781]
Process handles appear to be leaking in queries using an IN clause during concurrent DB access
	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-1831 	  	DERBY-1831 	]|| 	[DERBY-1831] 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-1831 	  	DERBY-1831 	]|| || 	[DERBY-1831]
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 	]|| 	[DERBY-2017] 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-2017 	  	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 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-2105 	  	DERBY-2105 	]|| 	[DERBY-2105] Network
Client - Column of type CHAR, VARCHAR or LONG VARCHAR contains wrong value after being updated
using the updateObject() method with a clob as parameter. 	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-2105 	  	DERBY-2105 	]|| || 	[DERBY-2105]
Network Client - Column of type CHAR, VARCHAR or LONG VARCHAR contains wrong value after being
updated using the updateObject() method with a clob as parameter. 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-2349 	  	DERBY-2349 	]|| 	[DERBY-2349] Accessing
a BLOB column twice in an INSERT trigger leads to errors in the value on-disk 	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-2349 	  	DERBY-2349 	]|| || 	[DERBY-2349]
Accessing a BLOB column twice in an INSERT trigger leads to errors in the value on-disk 	||
	||
- ||[https://issues.apache.org/jira/browse/DERBY-2602 	  	DERBY-2602 	]|| 	[DERBY-2602] TIMESTAMP
value is truncated when return to client 	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-2602 	  	DERBY-2602 	]|| || 	[DERBY-2602]
TIMESTAMP value is truncated when return to client 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-2861 	  	DERBY-2861 	]|| 	[DERBY-2861] Thread
safety issue in TableDescriptor 	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-2861 	  	DERBY-2861 	]|| || 	[DERBY-2861]
Thread safety issue in TableDescriptor 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-2990 	  	DERBY-2990 	]|| 	[DERBY-2990] ResultSet.getBlob
holds locks even with READ_UNCOMMITTED isolation level 	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-2990 	  	DERBY-2990 	]|| || 	[DERBY-2990]
ResultSet.getBlob holds locks even with READ_UNCOMMITTED isolation level 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-3023 	  	DERBY-3023 	]|| 	[DERBY-3023] Different
result rows depending on the sequence of INNER JOIN and OUTER JOIN 	|| wrong results	||
+ ||[https://issues.apache.org/jira/browse/DERBY-3023 	  	DERBY-3023 	]|| || 	[DERBY-3023]
Different result rows depending on the sequence of INNER JOIN and OUTER JOIN 	|| wrong results
||
- ||[https://issues.apache.org/jira/browse/DERBY-3083 	  	DERBY-3083 	]|| 	[DERBY-3083] Network
server demands a file called "derbynet.jar" in classpath 	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-3083 	  	DERBY-3083 	]|| || 	[DERBY-3083]
Network server demands a file called "derbynet.jar" in classpath 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-3087 	  	DERBY-3087 	]|| 	[DERBY-3087] NPE
while running the SVT MailJdbc 	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-3087 	  	DERBY-3087 	]|| || 	[DERBY-3087]
NPE while running the SVT MailJdbc 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-3094 	  	DERBY-3094 	]|| 	[DERBY-3094] Grouping
of expressions causes NullPointerException 	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-3094 	  	DERBY-3094 	]|| || 	[DERBY-3094]
Grouping of expressions causes NullPointerException 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-3115 	  	DERBY-3115 	]|| 	[DERBY-3115] 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-3115 	  	DERBY-3115 	]|| || 	[DERBY-3115]
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 	]|| 	[DERBY-700] Derby
does not prevent dual boot of database from different classloaders on Linux 	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-700 	  	DERBY-700 	]|| || 	[DERBY-700] Derby
does not prevent dual boot of database from different classloaders on Linux 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-723 	  	DERBY-723 	]|| 	[DERBY-723] Escaped
JDBC/ODBCC function CHAR(n) incorrect maps to Derby's builtin CHAR() function. 	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-723 	  	DERBY-723 	]|| || 	[DERBY-723] Escaped
JDBC/ODBCC function CHAR(n) incorrect maps to Derby's builtin CHAR() function. 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-728 	  	DERBY-728 	]|| 	[DERBY-728] Unable
to create databases whose name containg Chinese characters through the client driver 	|| 
||
+ ||[https://issues.apache.org/jira/browse/DERBY-728 	  	DERBY-728 	]|| || 	[DERBY-728] Unable
to create databases whose name containg Chinese characters through the client driver 	|| 
||
- ||[https://issues.apache.org/jira/browse/DERBY-2991 	  	DERBY-2991 	]||Index split deadlock
 	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-2991 	  	DERBY-2991 	]|| ||Index split deadlock
 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-1482 	  	DERBY-1482 	]||Update triggers on
tables with blob columns stream blobs into memory even when the blobs are not referenced/accessed.
	|| 	||
+ ||[https://issues.apache.org/jira/browse/DERBY-1482 	  	DERBY-1482 	]|| ||Update triggers
on tables with blob columns stream blobs into memory even when the blobs are not referenced/accessed.
	|| 	||
  

Mime
View raw message