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 Wed, 01 Aug 2007 22:32:54 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:
http://wiki.apache.org/db-derby/HighValueFixCandidates

------------------------------------------------------------------------------
  These are issues that would be great to see fixed for the 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] and 
  [https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310744
Regression Test Failures.]
+ 
  || JIRA_ISSUE   ||  SUMMARY    	|| COMMENTS||
  ||[https://issues.apache.org/jira/browse/DERBY-2972  	    	 DERBY-2972  	 ]||  	[DERBY-2972]
Update or select with function in the where clause causes with TERRITORY_BASED collation fails
with ERROR 42818: Comparisons between 'VARCHAR' and 'VARCHAR' are not supported.  	 ||  	
||
  ||[https://issues.apache.org/jira/browse/DERBY-2967 	  	DERBY-2967 	]|| 	[DERBY-2967] Single
character does not match high value unicode character with collation TERRITORY_BASED 	|| 
||
  ||[https://issues.apache.org/jira/browse/DERBY-2961 	  	DERBY-2961 	]|| 	[DERBY-2961] TriggerTest.testTypesINActionStatement
fails with 'ASSERT FAILED col1.getClass() (class org.apache.derby.iapi.types.SQLClob) expected
to be the same as col2.getClass() (class org.apache.derby.iapi.types.CollatorSQLClob) 	||
	||
  ||[https://issues.apache.org/jira/browse/DERBY-2957 	  	DERBY-2957 	]|| 	[DERBY-2957] ASSERT
FAILED col1.getClass() (class org.apache.derby.iapi.types.SQLChar) expected to be the same
as col2.getClass() (class org.apache.derby.iapi.types.CollatorSQLChar) in NistScripts dml002
test with collated database 	|| 	||
  ||[https://issues.apache.org/jira/browse/DERBY-2946 	  	DERBY-2946 	]|| 	[DERBY-2946] In
soft upgrade mode, the metadata queries do not get compiled in SYS schema. This will cause
problems in future releases of Derby. 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-2933 	  	DERBY-2933 	]|| 	[DERBY-2933] When
network server disconnects due to an I/O Exception it does not always log the exception that
caused the error 	|| 	||
  ||[https://issues.apache.org/jira/browse/DERBY-2905 	  	DERBY-2905 	]|| 	[DERBY-2905] Shutting
down embedded Derby does not remove all code, the AutoloadDriver is left registered in the
DriverManager. 	||regression in 10.2 ||
- ||[https://issues.apache.org/jira/browse/DERBY-2894 	  	DERBY-2894 	]|| 	[DERBY-2894] calling
DatabaseMetaData.getColumns() with % for matching column character in a territory based collated
db does not work in 1.4.2 jvms 	|| 	||
  ||[https://issues.apache.org/jira/browse/DERBY-2892 	  	DERBY-2892 	]|| 	[DERBY-2892] Closing
a resultset after retrieving a large > 32665 bytes value with Network Server does not release
locks 	||regression in 10.3 	||
  ||[https://issues.apache.org/jira/browse/DERBY-2649 	  	DERBY-2649 	]|| 	[DERBY-2649] An
unsuccessful boot attempt of an booted database can potentially delete files in the temp directory
that are in use. 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-2620 	  	DERBY-2620 	]|| 	[DERBY-2620] embedded
throws SQLState 8003 (No current connection) on rs.next() on closed resultSet in test for
DERBY-1025 in DataSourceTest 	|| 	||
  ||[https://issues.apache.org/jira/browse/DERBY-2576 	  	DERBY-2576 	]|| 	[DERBY-2576] setCreateDatabase
does not work for EmbeddedXADataSource or EmbeddedConnectionPoolDataSource 	|| 	||
  ||[https://issues.apache.org/jira/browse/DERBY-2436 	  	DERBY-2436 	]|| 	[DERBY-2436] SYSCS_IMPORT_TABLE
can be used to read derby files 	||Security hole	||
  ||[https://issues.apache.org/jira/browse/DERBY-2352 	  	DERBY-2352 	]|| 	[DERBY-2352] Assertion
Failure with order by and group by expression 	|| 	||
@@ -51, +49 @@

  ||[https://issues.apache.org/jira/browse/DERBY-1205 	  	DERBY-1205 	]|| 	[DERBY-1205] Unexpectedly
very slow performance compared to DB2 	|| 	||
  ||[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-1066 	  	DERBY-1066 	]|| 	[DERBY-1066] database
creation with log device as relative path under security manager throws NULL pointer excetpton
if there is NO acess permission for user.dir 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-1030 	  	DERBY-1030 	]|| 	[DERBY-1030] In
some situations a RETURNS NULL ON NULL function is called when one ot its parameters is NULL
	|| 	||
  ||[https://issues.apache.org/jira/browse/DERBY-1026 	  	DERBY-1026 	]|| 	[DERBY-1026] LDAP
with caching DNs in derby.user.userName as database property does not work 	|| 	||
  ||[https://issues.apache.org/jira/browse/DERBY-1018 	  	DERBY-1018 	]|| 	[DERBY-1018] Client
xa Statement.getConnection and DatabaseMetadata.getConnection returns underlying NetXAConnection
instead of Logical connection 	|| 	||
  ||[https://issues.apache.org/jira/browse/DERBY-974 	  	DERBY-974 	]|| 	[DERBY-974] ClientDriver
can lose some connection properties 	|| 	||
@@ -59, +56 @@

  ||[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-720 	  	DERBY-720 	]|| 	[DERBY-720] Calling
SYSCS_INPLACE_COMPRESS_TABLE on a synonym or a temp table results in a NullPointerException
	|| 	||
  ||[https://issues.apache.org/jira/browse/DERBY-588 	  	DERBY-588 	]|| 	[DERBY-588] database
created on zOS (os/390) cannot be used on windows 	|| 	||
- ||[https://issues.apache.org/jira/browse/DERBY-341 	  	DERBY-341 	]|| 	[DERBY-341] Client
should disallow XAConnection getConnection() when a global transaction has been started and
a logical connection has already been obtained 	|| 	||
  ||[https://issues.apache.org/jira/browse/DERBY-269 	  	DERBY-269 	]|| 	[DERBY-269] Provide
some way to update index cardinality statistics (e.g. reimplement update statistics) 	||often
hit by users ||
  

Mime
View raw message