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 "DerbyTenThreeRelease" by OysteinGrovlen
Date Wed, 24 Jan 2007 12:02:14 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 OysteinGrovlen:
http://wiki.apache.org/db-derby/DerbyTenThreeRelease

------------------------------------------------------------------------------
  || Feature || Description || Associated JIRAs ||
  || Alter Table || You can now DROP or RENAME a column. Together with a number of enhancements
in 10.2, this means that most dynamic schema modifications are now possible || DERBY-396,
DERBY-165, DERBY-726, DERBY-1489, DERBY-1490, DERBY-1926, DERBY-1909, DERBY-1515, DERBY-2042||
  || SSL/TLS || Implement SSL/TLS communication between client and server || [https://issues.apache.org/jira/browse/DERBY-2108
DERBY-2108] ||
+ || Blob/Clob API || Implement JDBC methods for Blob/Clob that are currently not supported
|| [https://issues.apache.org/jira/browse/DERBY-1341 DERBY-1341], [https://issues.apache.org/jira/browse/DERBY-1285
DERBY-1285], [https://issues.apache.org/jira/browse/DERBY-1286 DERBY-1286] ||
  
  == 10.3 Non-functional Improvements ==
  
@@ -36, +37 @@

  || Performance || Reduce CPU usage in embedded Derby. Main areas being worked on are: Lock
manager and latching, reduced use of synchronized data structures, optimize use of bit sets.||
DERBY-1704, DERBY-2107, DERBY-2149, DERBY-2150, DERBY-2191, DERBY-2226 ||
  || Performance || Improve Derby's treatment of IN-lists to allow the optimizer to consider
using indexes when appropriate.  || [https://issues.apache.org/jira/browse/DERBY-47 DERBY-47],
[https://issues.apache.org/jira/browse/DERBY-713 DERBY-713] ||
  || Testing || Switch testing to be pure JUnit based. || [https://issues.apache.org/jira/browse/DERBY-1952
DERBY-1952] & many others ||
+ || Memory Usage || Avoid having to materialize entire LOBs in network client.  The client
will use locators when requesting operations to be performed on LOBs stored on the server
side. || Master JIRA: [https://issues.apache.org/jira/browse/DERBY-208 DERBY-208] ||
  
  == 10.3 Bug Fix Candidates ==
  

Mime
View raw message