db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d..@apache.org
Subject svn commit: rev 54005 - incubator/derby/site/trunk/src/documentation/content/xdocs
Date Thu, 07 Oct 2004 18:31:29 GMT
Author: djd
Date: Thu Oct  7 11:31:29 2004
New Revision: 54005

Modified:
   incubator/derby/site/trunk/src/documentation/content/xdocs/DerbyToDo.ihtml
Log:
Update the to-do document based upon discussions in the mailing lists.


Modified: incubator/derby/site/trunk/src/documentation/content/xdocs/DerbyToDo.ihtml
==============================================================================
--- incubator/derby/site/trunk/src/documentation/content/xdocs/DerbyToDo.ihtml	(original)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/DerbyToDo.ihtml	Thu Oct  7 11:31:29 2004
@@ -1,1062 +1,1216 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
-	<TITLE>Apache Derby: To-Do List</TITLE>
-	<META NAME="GENERATOR" CONTENT="OpenOffice.org 1.1.2  (Win32)">
-	<META NAME="AUTHOR" CONTENT="D D">
-	<META NAME="CREATED" CONTENT="20040811;8485880">
-	<META NAME="CHANGEDBY" CONTENT="D D">
-	<META NAME="CHANGED" CONTENT="20040812;16064387">
-	<STYLE>
-	<!--
-		@page { size: 8.5in 11in }
-	-->
-	</STYLE>
-</HEAD>
-<BODY LANG="en-US" DIR="LTR">
-<H1 ALIGN=CENTER>Overview</H1>
-<P><B>Last Update 2004/08/12</B></P>
-<P>This is a list of work items for Derby that are either actively
-been worked on, potential new items or items that were rejected by
-the community. Completed items will remain on the list for some time,
-e.g. Until they are documented and part of a stable line. This is
-only for items related to the Java code. Documentation, integration
-white-papers and web-site items are not covered here.</P>
-<P>Bugs are tracked separately in the Jira bug tracking system at
-&lt;LINK TO JIRA&gt;.</P>
-<P>As possible new items get discussed or requested on the user or
-developer mailing lists, or from any other channel, they should be
-added here.</P>
-<P>The explanation of the columns are:</P>
-<UL>
-	<LI><P><B>First column</B> &ndash; feature description.</P>
-	<LI><P><B>Approved</B> &ndash; Approval state</P>
-	<LI><P><B>blank</B> - no vote has been taken</P>
-	<LI><P><B>Yes</B> - item has been approved. Some linkage will be
-	provided to the vote, e.g. Date of vote.</P>
-	<LI><P><B>No</B> &ndash; item was not approved by the community.
-	Some linkage will be provided to the vote.</P>
-	<LI><P><B>Contact</B> &ndash; Contributors either actively working
-	on the item, or have some knowledge of the item.<BR>If blank then
-	get involved by starting a discussion of the item on the developer
-	mailing list. See the 'how it works' for details.<BR>If not blank
-	and you are interested then contact the current contributors to see
-	how you can help out.</P>
-	<LI><P><B>Progress</B> &ndash; Some description of where the item
-	stands.</P>
-	<LI><P><B>Comments</B> &ndash; More information on the feature,
-	maybe a link to a fuller description of the item, indication of
-	interest in the item etc.</P>
-</UL>
-<H1>Features</H1>
-<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>SQL</FONT></FONT></P>
-<TABLE WIDTH=100% BORDER=1 CELLPADDING=4 CELLSPACING=3>
-	<COL WIDTH=64*>
-	<COL WIDTH=18*>
-	<COL WIDTH=46*>
-	<COL WIDTH=64*>
-	<COL WIDTH=64*>
-	<THEAD>
-		<TR VALIGN=TOP>
-			<TH WIDTH=25%>
-				<P>SQL Feature</P>
-			</TH>
-			<TH WIDTH=7%>
-				<P>Approved</P>
-			</TH>
-			<TH WIDTH=18%>
-				<P>Contact</P>
-			</TH>
-			<TH WIDTH=25%>
-				<P>Progress</P>
-			</TH>
-			<TH WIDTH=25%>
-				<P>Comments</P>
-			</TH>
-		</TR>
-	</THEAD>
-	<TBODY>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>GRANT/REVOKE</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>none</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Standard SQL92, some demand from community.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>SQL/XML</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P>Armageddon R Brown, Satheesh Bandaram, Cliff Leung</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Prototype code</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>XML data type and SQL/XML functions using Xerces as the
-				parser. Need to break this into separate items, one per
-				conformance item in SQL/XML.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>XQuery support</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P>Armageddon R Brown, Satheesh Bandaram, Cliff Leung</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Prototype code</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Some prototype code for Xpath expressions.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>SPECIFIC name for PROCEDUREs and FUNCTIONs</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Catalogs and parser are set up to handle a SPECIFIC name.</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>SPECIFIC name is a step towards overloading of PROCEDUREs and
-				FUNCTIONs.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Overloading of PROCEDUREs and FUNCTIONs</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>none</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Allows multiple PROCEDUREs and FUNCTIONs with the same name
-				but different parameter types.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>SQL Procedure language</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>none</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Would need to be standard based but then would that limit its
-				use as applications that use it might not be able to migrate up
-				to other databases. Need to investigate overlap of standard
-				options with vendor specific procedure language.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>TRUNCATE TABLE</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P>Suresh Thalamati</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Code basically complete in engine, needs to be exposed</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Details of rollback behaviour to be clarified.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>National character types (NCHAR etc.)</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Code basically complete in engine, need to be exposed and
-				verified with SQL standard.</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Code could also use cleanup and ensure casts between types is
-				handled correctly.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Multi-version concurrency locking (like Oracle, MySQL etc.)</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>None</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P><BR>
-				</P>
-			</TD>
-		</TR>
-	</TBODY>
-</TABLE>
-<P><BR><BR>
-</P>
-<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>JDBC</FONT></FONT></P>
-<TABLE WIDTH=100% BORDER=1 CELLPADDING=4 CELLSPACING=3>
-	<COL WIDTH=64*>
-	<COL WIDTH=16*>
-	<COL WIDTH=48*>
-	<COL WIDTH=64*>
-	<COL WIDTH=64*>
-	<THEAD>
-		<TR VALIGN=TOP>
-			<TH WIDTH=25%>
-				<P>JDBC Feature</P>
-			</TH>
-			<TH WIDTH=6%>
-				<P>Approved</P>
-			</TH>
-			<TH WIDTH=19%>
-				<P>Contact</P>
-			</TH>
-			<TH WIDTH=25%>
-				<P>Progress</P>
-			</TH>
-			<TH WIDTH=25%>
-				<P>Comments</P>
-			</TH>
-		</TR>
-	</THEAD>
-	<TBODY>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Updateable ResultSets</P>
-			</TD>
-			<TD WIDTH=6%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=19%>
-				<P>Mamta Satoor</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>concept</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>JDBC 3.0</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Support update methods in java.sql.{Blob,Clob}</P>
-			</TD>
-			<TD WIDTH=6%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=19%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>none</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P><BR>
-				</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>JDBC 4.0 support</P>
-			</TD>
-			<TD WIDTH=6%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=19%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Place-holder</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>JDBC 4.0 specification is in progress as JSR 221. Most likely
-				this would split into a number of items, one per feature of JDBC
-				4.0.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Query timeout</P>
-			</TD>
-			<TD WIDTH=6%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=19%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>concept</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Java.sql.Statement.setQueryTimeout</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>JSR 169 support<BR>JDBC Optional Package for CDC/Foundation
-				Profile 
-				</P>
-			</TD>
-			<TD WIDTH=6%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=19%>
-				<P>Dan Debrunner, Myrna Van lunteren</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Partial framework</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Requires J2ME/CDC/Foundation support. Convert old framework
-				for JDBC 1.2 support to JSR169.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>XA support with Network Server</P>
-			</TD>
-			<TD WIDTH=6%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=19%>
-				<P>Katherine Marsden</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Prototype code</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Support for JCC's java.sql.XADataSource implementation for use
-				in application servers.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Support java.sql.Statement.cancel() 
-				</P>
-			</TD>
-			<TD WIDTH=6%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=19%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>None</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>related to query timeout</P>
-			</TD>
-		</TR>
-	</TBODY>
-</TABLE>
-<P><BR><BR>
-</P>
-<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>Platform
-Support</FONT></FONT></P>
-<TABLE WIDTH=100% BORDER=1 CELLPADDING=4 CELLSPACING=3>
-	<COL WIDTH=64*>
-	<COL WIDTH=17*>
-	<COL WIDTH=47*>
-	<COL WIDTH=64*>
-	<COL WIDTH=64*>
-	<THEAD>
-		<TR VALIGN=TOP>
-			<TH WIDTH=25%>
-				<P>Platform Support</P>
-			</TH>
-			<TH WIDTH=7%>
-				<P>Approved</P>
-			</TH>
-			<TH WIDTH=18%>
-				<P>Contact</P>
-			</TH>
-			<TH WIDTH=25%>
-				<P>Progress</P>
-			</TH>
-			<TH WIDTH=25%>
-				<P>Comments</P>
-			</TH>
-		</TR>
-	</THEAD>
-	<TBODY>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>J2ME/CDC/Foundation support</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P>Dan Debrunner, Myrna Van lunteren</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Some initial work already in</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Need to remove use of classes that are not in the profile,
-				such as java.math.BigDecimal, java.util.Stack, etc. Set up
-				compile to use those libraries as the base compile class path.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>OSGi ee.minimum support</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P>Dan Debrunner, Myrna Van lunteren</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Some initial work already in</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Is a sub-set of J2ME/CDC/Foundation</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>JDK 1.5</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Place holder</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Look into seeing if there are specific features of JDK 1.5
-				that would benefit Derby.Most likely would split into multiple
-				items.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>J2EE 1.5</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Place holder</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Specific JBDC requirements of J2EE 1.5.Most likely would split
-				into multiple items.</P>
-			</TD>
-		</TR>
-	</TBODY>
-</TABLE>
-<P><BR><BR>
-</P>
-<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>Other</FONT></FONT></P>
-<P>Miscellaneous features, such as extensibility (pluggable code), or
-security features.</P>
-<TABLE WIDTH=100% BORDER=1 CELLPADDING=4 CELLSPACING=3>
-	<COL WIDTH=64*>
-	<COL WIDTH=17*>
-	<COL WIDTH=47*>
-	<COL WIDTH=64*>
-	<COL WIDTH=64*>
-	<THEAD>
-		<TR VALIGN=TOP>
-			<TH WIDTH=25%>
-				<P>Platform Support</P>
-			</TH>
-			<TH WIDTH=7%>
-				<P>Approved</P>
-			</TH>
-			<TH WIDTH=18%>
-				<P>Contact</P>
-			</TH>
-			<TH WIDTH=25%>
-				<P>Progress</P>
-			</TH>
-			<TH WIDTH=25%>
-				<P>Comments</P>
-			</TH>
-		</TR>
-	</THEAD>
-	<TBODY>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Dynamic swap of derby.log</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>none</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Better mechanisms for handling the error log with a long
-				running system. E.g. Switch log files every 100k bytes.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Backup directly to jar file</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>none</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Make the backup code directly create a jar file. Allows easy
-				creation of jar files for 'database-in-a jar 'feature</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Generate run time statistics output in XML format</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>none</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Might reduce footprint by not requiring specific classes for
-				each ResultSet type</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Text search/indexing</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>none</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Pluggable mechanism to support text indexing engines, how to
-				make SQL queries standard?</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Migration tool</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>None</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Support migration from an existing JDBC database to Derby.
-				Support any JDBC database with standard datatypes and older
-				Cloudscape releases.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>In-memory database</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P>Jack Klebanoff</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Prototype code</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Implementation of the org.apache.derby.io package that
-				provides an in-memory database</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Single file per database</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>None</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Rather than a single file per table.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Property validation (derby.*)</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Framework and validation for some properties</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Validation for all properties</P>
-			</TD>
-		</TR>
-	</TBODY>
-</TABLE>
-<H1>Performance/Zero Admin/Footprint</H1>
-<P><BR><BR>
-</P>
-<TABLE WIDTH=100% BORDER=1 CELLPADDING=4 CELLSPACING=3>
-	<COL WIDTH=64*>
-	<COL WIDTH=17*>
-	<COL WIDTH=47*>
-	<COL WIDTH=64*>
-	<COL WIDTH=64*>
-	<THEAD>
-		<TR VALIGN=TOP>
-			<TH WIDTH=25%>
-				<P>Platform Support</P>
-			</TH>
-			<TH WIDTH=7%>
-				<P>Approved</P>
-			</TH>
-			<TH WIDTH=18%>
-				<P>Contact</P>
-			</TH>
-			<TH WIDTH=25%>
-				<P>Progress</P>
-			</TH>
-			<TH WIDTH=25%>
-				<P>Comments</P>
-			</TH>
-		</TR>
-	</THEAD>
-	<TBODY>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Smarter query recompilation</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Some ideas</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>The current scheme of check every N iterations is simplistic
-				and can be expensive. Also information about which piece of the
-				query was badly estimated is there but not used.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Autonomic checkpointing timing and log file size</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P>Sunitha Kambhampati</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Some ideas</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Current checkpoint interval and log file saize can be
-				configured, but engine should self-configure.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Use of idle time for background checkpoint</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P><BR>
-				</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Optimizer overrides</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P>Satheesh Bandaram</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Overrides exist in the code but are not exposed</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Provide optimizer overrides (e.g force join order) using a
-				mechanism that does not require the application's SQL to change
-				(and thus become non-portable). E.g. A separate configuration
-				that indicates the join order for a SQL text string.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Single background thread</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P>Dan Debrunner</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>ideas</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Currently one background thread is created per database, which
-				becomes an issue when supporting thousands of databases per JVM.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Improved statement plan cache</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P>Dan Debrunner</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Some framework code exists</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Make single-use (DDL) statements indicate they don't need to
-				be cached, support single plan regardless of compilation schema
-				if they do not depend on the current schema</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Background space re-claiming</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P>Mike Matrigali</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Some design</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Allow space to be returned to the operating system by
-				truncating files. Have to move rows around dynamically etc.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Support super-simple configuration of single configuration
-				parameter &ndash; how much total memory to use</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Some memory based sizing support for the cache</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>All caches would re-size themselves based upon the value and
-				their size and number of connections etc.</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Backward scan in index</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>??</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P><BR>
-				</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P>Implement limt on on-disk database size</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>None</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P>Limit database growth.</P>
-			</TD>
-		</TR>
-	</TBODY>
-</TABLE>
-<H1>Code Cleanup</H1>
-<P><BR><BR>
-</P>
-<TABLE WIDTH=100% BORDER=1 CELLPADDING=4 CELLSPACING=3>
-	<COL WIDTH=64*>
-	<COL WIDTH=17*>
-	<COL WIDTH=47*>
-	<COL WIDTH=64*>
-	<COL WIDTH=64*>
-	<THEAD>
-		<TR VALIGN=TOP>
-			<TH WIDTH=25%>
-				<P>Platform Support</P>
-			</TH>
-			<TH WIDTH=7%>
-				<P>Approved</P>
-			</TH>
-			<TH WIDTH=18%>
-				<P>Contact</P>
-			</TH>
-			<TH WIDTH=25%>
-				<P>Progress</P>
-			</TH>
-			<TH WIDTH=25%>
-				<P>Comments</P>
-			</TH>
-		</TR>
-	</THEAD>
-	<TBODY>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P><BR>
-				</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P><BR>
-				</P>
-			</TD>
-		</TR>
-		<TR VALIGN=TOP>
-			<TD WIDTH=25%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=7%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=18%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P><BR>
-				</P>
-			</TD>
-			<TD WIDTH=25%>
-				<P><BR>
-				</P>
-			</TD>
-		</TR>
-	</TBODY>
-</TABLE>
-<P STYLE="margin-bottom: 0in"><BR>
-</P>
-</BODY>
-</HTML>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+	<TITLE>Apache Derby: To-Do List</TITLE>
+	<META NAME="GENERATOR" CONTENT="OpenOffice.org 1.1.2  (Win32)">
+	<META NAME="AUTHOR" CONTENT="D D">
+	<META NAME="CREATED" CONTENT="20040811;8485880">
+	<META NAME="CHANGEDBY" CONTENT="D D">
+	<META NAME="CHANGED" CONTENT="20041007;10332819">
+	<STYLE>
+	<!--
+		@page { size: 8.5in 11in }
+	-->
+	</STYLE>
+</HEAD>
+<BODY LANG="en-US" DIR="LTR">
+<H1 ALIGN=CENTER>Overview</H1>
+<P><B>Last Update 2004/10/07</B></P>
+<P>This is a list of work items for Derby that are either actively
+been worked on, potential new items or items that were rejected by
+the community. Completed items will remain on the list for some time,
+e.g. Until they are documented and part of a release. This is only
+for items related to the Java code. Documentation, integration
+white-papers and web-site items are not covered here.</P>
+<P>Bugs are tracked separately in the Jira bug tracking system at
+<A HREF="http://issues.apache.org/jira/browse/DERBY">http://issues.apache.org/jira/browse/DERBY</A>.
+Feature requests may also exist in Jira.</P>
+<P>As possible new items get discussed or requested on the user or
+developer mailing lists, or from any other channel, they should be
+added here.</P>
+<P>The explanation of the columns are:</P>
+<UL>
+	<LI><P><B>First column</B> &ndash; feature description.</P>
+	<LI><P><B>Approved</B> &ndash; Approval state</P>
+	<LI><P><B>blank</B> - no vote has been taken</P>
+	<LI><P><B>Yes</B> - item has been approved. Some linkage will be
+	provided to the vote, e.g. Date of vote.</P>
+	<LI><P><B>No</B> &ndash; item was not approved by the community.
+	Some linkage will be provided to the vote.</P>
+	<LI><P><B>Contact</B> &ndash; Contributors either actively working
+	on the item, or have some knowledge of the item.<BR>If blank then
+	get involved by starting a discussion of the item on the developer
+	mailing list. See the 'how it works' for details.<BR>If not blank
+	and you are interested then contact the current contributors to see
+	how you can help out.</P>
+	<LI><P><B>Progress</B> &ndash; Some description of where the item
+	stands.</P>
+	<LI><P><B>Comments</B> &ndash; More information on the feature,
+	maybe a link to a fuller description of the item, indication of
+	interest in the item etc.</P>
+</UL>
+<H1>Features</H1>
+<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>SQL</FONT></FONT></P>
+<TABLE WIDTH=100% BORDER=1 CELLPADDING=4 CELLSPACING=3>
+	<COL WIDTH=64*>
+	<COL WIDTH=18*>
+	<COL WIDTH=46*>
+	<COL WIDTH=64*>
+	<COL WIDTH=64*>
+	<THEAD>
+		<TR VALIGN=TOP>
+			<TH WIDTH=25%>
+				<P>SQL Feature</P>
+			</TH>
+			<TH WIDTH=7%>
+				<P>Approved</P>
+			</TH>
+			<TH WIDTH=18%>
+				<P>Contact</P>
+			</TH>
+			<TH WIDTH=25%>
+				<P>Progress</P>
+			</TH>
+			<TH WIDTH=25%>
+				<P>Comments</P>
+			</TH>
+		</TR>
+	</THEAD>
+	<TBODY>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>ALTER TABLE DROP COLUMN</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><A HREF="http://nagoya.apache.org/eyebrowse/BrowseList?listName=derby-dev@db.apache.org&amp;from=892740&amp;to=892740&amp;count=2&amp;by=thread&amp;paged=false">derby-dev
+				thread</A></P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>COMMENT ON</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><A HREF="http://nagoya.apache.org/eyebrowse/BrowseList?listName=derby-dev@db.apache.org&amp;from=881380&amp;to=881380&amp;count=10&amp;by=thread&amp;paged=false">derby-dev
+				thread</A></P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>User Defined Types</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><A HREF="http://nagoya.apache.org/eyebrowse/BrowseList?listName=derby-dev@db.apache.org&amp;from=876376&amp;to=876376&amp;count=7&amp;by=thread&amp;paged=false">derby-dev
+				thread</A></P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Increased SQL identifier lengths</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><A HREF="http://nagoya.apache.org/eyebrowse/BrowseList?listName=derby-dev@db.apache.org&amp;from=886117&amp;to=886117&amp;count=9&amp;by=thread&amp;paged=false">derby-dev
+				thread</A></P>
+				<P>and mentions in a couple of other threads</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Gist indexing (spatial)</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><A HREF="http://nagoya.apache.org/eyebrowse/BrowseList?listName=derby-dev@db.apache.org&amp;from=883906&amp;to=883906&amp;count=1&amp;by=thread&amp;paged=false">derby-dev
+				thread</A></P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Localized character sorting</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><A HREF="http://nagoya.apache.org/eyebrowse/BrowseList?listName=derby-dev@db.apache.org&amp;from=886768&amp;to=886768&amp;count=3&amp;by=thread&amp;paged=false">derby-dev
+				thread</A></P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>GRANT/REVOKE</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>none</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Standard SQL92, some demand from community.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>SQL/XML</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P>Armageddon R Brown, Satheesh Bandaram, Cliff Leung</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Prototype code</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>XML data type and SQL/XML functions using Xerces as the
+				parser. Need to break this into separate items, one per
+				conformance item in SQL/XML.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>XQuery support</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P>Armageddon R Brown, Satheesh Bandaram, Cliff Leung</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Prototype code</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Some prototype code for Xpath expressions.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>SPECIFIC name for PROCEDUREs and FUNCTIONs</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Catalogs and parser are set up to handle a SPECIFIC name.</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>SPECIFIC name is a step towards overloading of PROCEDUREs and
+				FUNCTIONs.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Overloading of PROCEDUREs and FUNCTIONs</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><A HREF="http://nagoya.apache.org/eyebrowse/BrowseList?listName=derby-dev@db.apache.org&amp;from=896689&amp;to=896689&amp;count=3&amp;by=thread&amp;paged=false">derby-dev
+				thread</A></P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>none</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Allows multiple PROCEDUREs and FUNCTIONs with the same name
+				but different parameter types.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>SQL Procedure language</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>none</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Would need to be standard based but then would that limit its
+				use as applications that use it might not be able to migrate up
+				to other databases. Need to investigate overlap of standard
+				options with vendor specific procedure language.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>TRUNCATE TABLE</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P>Suresh Thalamati</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Code basically complete in engine, needs to be exposed</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Details of rollback behaviour to be clarified.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>National character types (NCHAR etc.)</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Code basically complete in engine, need to be exposed and
+				verified with SQL standard.</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Code could also use cleanup and ensure casts between types is
+				handled correctly.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Multi-version concurrency locking (like Oracle, MySQL etc.)</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>None</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+		</TR>
+	</TBODY>
+</TABLE>
+<P><BR><BR>
+</P>
+<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>JDBC</FONT></FONT></P>
+<TABLE WIDTH=100% BORDER=1 CELLPADDING=4 CELLSPACING=3>
+	<COL WIDTH=64*>
+	<COL WIDTH=16*>
+	<COL WIDTH=48*>
+	<COL WIDTH=64*>
+	<COL WIDTH=64*>
+	<THEAD>
+		<TR VALIGN=TOP>
+			<TH WIDTH=25%>
+				<P>JDBC Feature</P>
+			</TH>
+			<TH WIDTH=6%>
+				<P>Approved</P>
+			</TH>
+			<TH WIDTH=19%>
+				<P>Contact</P>
+			</TH>
+			<TH WIDTH=25%>
+				<P>Progress</P>
+			</TH>
+			<TH WIDTH=25%>
+				<P>Comments</P>
+			</TH>
+		</TR>
+	</THEAD>
+	<TBODY>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Updateable ResultSets</P>
+			</TD>
+			<TD WIDTH=6%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=19%>
+				<P>Mamta Satoor</P>
+				<P><A HREF="http://nagoya.apache.org/eyebrowse/BrowseList?listName=derby-dev@db.apache.org&amp;from=884594&amp;to=884594&amp;count=2&amp;by=thread&amp;paged=false">derby-dev
+				thread</A></P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Actively being worked on</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>JDBC 3.0</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Support update methods in java.sql.{Blob,Clob}</P>
+			</TD>
+			<TD WIDTH=6%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=19%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>none</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>JDBC 4.0 support</P>
+			</TD>
+			<TD WIDTH=6%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=19%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Place-holder</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>JDBC 4.0 specification is in progress as JSR 221. Most likely
+				this would split into a number of items, one per feature of JDBC
+				4.0.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Query timeout</P>
+			</TD>
+			<TD WIDTH=6%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=19%>
+				<P><A HREF="http://nagoya.apache.org/jira/browse/DERBY-31">DERBY-31</A></P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>concept</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Java.sql.Statement.setQueryTimeout</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>JSR 169 support<BR>JDBC Optional Package for CDC/Foundation
+				Profile 
+				</P>
+			</TD>
+			<TD WIDTH=6%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=19%>
+				<P>Dan Debrunner, Myrna Van lunteren</P>
+				<P><A HREF="http://nagoya.apache.org/eyebrowse/BrowseList?listName=derby-dev@db.apache.org&amp;from=893545&amp;to=893545&amp;count=6&amp;by=thread&amp;paged=false">derby-dev
+				thread</A></P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Actively being worked on</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Requires J2ME/CDC/Foundation support. Convert old framework
+				for JDBC 1.2 support to JSR169.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>XA support with Network Server</P>
+			</TD>
+			<TD WIDTH=6%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=19%>
+				<P>Katherine Marsden<BR><A HREF="http://issues.apache.org/jira/browse/DERBY-10">DERBY-10</A></P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Actively being worked on</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Support for JCC's java.sql.XADataSource implementation for use
+				in application servers.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Support java.sql.Statement.cancel() 
+				</P>
+			</TD>
+			<TD WIDTH=6%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=19%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>None</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>related to query timeout</P>
+			</TD>
+		</TR>
+	</TBODY>
+</TABLE>
+<P><BR><BR>
+</P>
+<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>Platform
+Support</FONT></FONT></P>
+<TABLE WIDTH=100% BORDER=1 CELLPADDING=4 CELLSPACING=3>
+	<COL WIDTH=64*>
+	<COL WIDTH=17*>
+	<COL WIDTH=47*>
+	<COL WIDTH=64*>
+	<COL WIDTH=64*>
+	<THEAD>
+		<TR VALIGN=TOP>
+			<TH WIDTH=25%>
+				<P>Platform Support</P>
+			</TH>
+			<TH WIDTH=7%>
+				<P>Approved</P>
+			</TH>
+			<TH WIDTH=18%>
+				<P>Contact</P>
+			</TH>
+			<TH WIDTH=25%>
+				<P>Progress</P>
+			</TH>
+			<TH WIDTH=25%>
+				<P>Comments</P>
+			</TH>
+		</TR>
+	</THEAD>
+	<TBODY>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>J2ME/CDC/Foundation support</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P>Dan Debrunner, Myrna Van lunteren</P>
+				<P>(See JSR169)</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Actively being worked on</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Need to remove use of classes that are not in the profile,
+				such as java.math.BigDecimal, java.util.Stack, etc. Set up
+				compile to use those libraries as the base compile class path.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>OSGi ee.minimum support</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P>Dan Debrunner, Myrna Van lunteren</P>
+				<P>(See JSR169)</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Some initial work already in</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Is a sub-set of J2ME/CDC/Foundation</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>JDK 1.5</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Place holder</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Look into seeing if there are specific features of JDK 1.5
+				that would benefit Derby.Most likely would split into multiple
+				items.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>J2EE 1.5</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Place holder</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Specific JBDC requirements of J2EE 1.5.Most likely would split
+				into multiple items.</P>
+			</TD>
+		</TR>
+	</TBODY>
+</TABLE>
+<P><BR><BR>
+</P>
+<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>Other</FONT></FONT></P>
+<P>Miscellaneous features, such as extensibility (pluggable code), or
+security features.</P>
+<TABLE WIDTH=100% BORDER=1 CELLPADDING=4 CELLSPACING=3>
+	<COL WIDTH=64*>
+	<COL WIDTH=17*>
+	<COL WIDTH=47*>
+	<COL WIDTH=64*>
+	<COL WIDTH=64*>
+	<THEAD>
+		<TR VALIGN=TOP>
+			<TH WIDTH=25%>
+				<P>Platform Support</P>
+			</TH>
+			<TH WIDTH=7%>
+				<P>Approved</P>
+			</TH>
+			<TH WIDTH=18%>
+				<P>Contact</P>
+			</TH>
+			<TH WIDTH=25%>
+				<P>Progress</P>
+			</TH>
+			<TH WIDTH=25%>
+				<P>Comments</P>
+			</TH>
+		</TR>
+	</THEAD>
+	<TBODY>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Dynamic swap of derby.log</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>none</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Better mechanisms for handling the error log with a long
+				running system. E.g. Switch log files every 100k bytes.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Backup directly to jar file</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>none</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Make the backup code directly create a jar file. Allows easy
+				creation of jar files for 'database-in-a jar 'feature</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Generate run time statistics output in XML format</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>none</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Might reduce footprint by not requiring specific classes for
+				each ResultSet type</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Text search/indexing</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>none</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Pluggable mechanism to support text indexing engines, how to
+				make SQL queries standard?</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Migration tool</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>None</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Support migration from an existing JDBC database to Derby.
+				Support any JDBC database with standard datatypes and older
+				Cloudscape releases.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>In-memory database</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P>Jack Klebanoff</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Prototype code</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Implementation of the org.apache.derby.io package that
+				provides an in-memory database</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Single file per database</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>None</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Rather than a single file per table.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Property validation (derby.*)</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Framework and validation for some properties</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Validation for all properties</P>
+			</TD>
+		</TR>
+	</TBODY>
+</TABLE>
+<H1>Performance/Zero Admin/Footprint</H1>
+<P><BR><BR>
+</P>
+<TABLE WIDTH=100% BORDER=1 CELLPADDING=4 CELLSPACING=3>
+	<COL WIDTH=64*>
+	<COL WIDTH=17*>
+	<COL WIDTH=47*>
+	<COL WIDTH=64*>
+	<COL WIDTH=64*>
+	<THEAD>
+		<TR VALIGN=TOP>
+			<TH WIDTH=25%>
+				<P>Platform Support</P>
+			</TH>
+			<TH WIDTH=7%>
+				<P>Approved</P>
+			</TH>
+			<TH WIDTH=18%>
+				<P>Contact</P>
+			</TH>
+			<TH WIDTH=25%>
+				<P>Progress</P>
+			</TH>
+			<TH WIDTH=25%>
+				<P>Comments</P>
+			</TH>
+		</TR>
+	</THEAD>
+	<TBODY>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Query re-writes for queries with constants</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><A HREF="http://nagoya.apache.org/eyebrowse/BrowseList?listName=derby-dev@db.apache.org&amp;from=878879&amp;to=878879&amp;count=4&amp;by=thread&amp;paged=false">derby-dev
+				thread</A></P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Smarter query recompilation</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Some ideas</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>The current scheme of check every N iterations is simplistic
+				and can be expensive. Also information about which piece of the
+				query was badly estimated is there but not used.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Autonomic checkpointing timing and log file size</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P>Sunitha Kambhampati</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Some ideas</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Current checkpoint interval and log file saize can be
+				configured, but engine should self-configure.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Use of idle time for background checkpoint</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Optimizer overrides</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P>Satheesh Bandaram</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Overrides exist in the code but are not exposed</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Provide optimizer overrides (e.g force join order) using a
+				mechanism that does not require the application's SQL to change
+				(and thus become non-portable). E.g. A separate configuration
+				that indicates the join order for a SQL text string.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Single background thread</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P>Dan Debrunner</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>ideas</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Currently one background thread is created per database, which
+				becomes an issue when supporting thousands of databases per JVM.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Improved statement plan cache</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P>Dan Debrunner</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Some framework code exists</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Make single-use (DDL) statements indicate they don't need to
+				be cached, support single plan regardless of compilation schema
+				if they do not depend on the current schema</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Background space re-claiming</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P>Mike Matrigali</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Some design</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Allow space to be returned to the operating system by
+				truncating files. Have to move rows around dynamically etc.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Support super-simple configuration of single configuration
+				parameter &ndash; how much total memory to use</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Some memory based sizing support for the cache</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>All caches would re-size themselves based upon the value and
+				their size and number of connections etc.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Backward scan in index</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>??</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P>Implement limt on on-disk database size</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>None</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P>Limit database growth.</P>
+			</TD>
+		</TR>
+	</TBODY>
+</TABLE>
+<H1>Code Cleanup</H1>
+<P><BR><BR>
+</P>
+<TABLE WIDTH=100% BORDER=1 CELLPADDING=4 CELLSPACING=3>
+	<COL WIDTH=64*>
+	<COL WIDTH=17*>
+	<COL WIDTH=47*>
+	<COL WIDTH=64*>
+	<COL WIDTH=64*>
+	<THEAD>
+		<TR VALIGN=TOP>
+			<TH WIDTH=25%>
+				<P>Platform Support</P>
+			</TH>
+			<TH WIDTH=7%>
+				<P>Approved</P>
+			</TH>
+			<TH WIDTH=18%>
+				<P>Contact</P>
+			</TH>
+			<TH WIDTH=25%>
+				<P>Progress</P>
+			</TH>
+			<TH WIDTH=25%>
+				<P>Comments</P>
+			</TH>
+		</TR>
+	</THEAD>
+	<TBODY>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=7%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=18%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=25%>
+				<P><BR>
+				</P>
+			</TD>
+		</TR>
+	</TBODY>
+</TABLE>
+<P STYLE="margin-bottom: 0in"><BR>
+</P>
+</BODY>
+</HTML>
\ No newline at end of file

Mime
View raw message