Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Date: Thu, 09 Jun 2005 15:04:01 -0400
From: "Lance J. Andersen" <Lance.Andersen@Sun.COM>
Subject: Re: [jira] Updated: (DERBY-334) Add initial SQL support for XML
 datatype/functions in Derby,  based on SQL/XML specs.
In-reply-to: <42A88D6E.2010808@Sourcery.Org>
To: Derby Development <derby-dev@db.apache.org>
Message-id: <42A892A1.6080602@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_DhAJ/+lXeU+82pJOP4xMCA)"
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2)
 Gecko/20040804 Netscape/7.2 (ax)
References: <796775295.1118277915320.JavaMail.jira@ajax.apache.org>
 <42A86739.6040906@debrunners.com> <42A88D6E.2010808@Sourcery.Org>

This is a multi-part message in MIME format.

--Boundary_(ID_DhAJ/+lXeU+82pJOP4xMCA)
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT

At somepoint, it would be worthwhile to discuss which J2SE versions to 
support. 

Satheesh Bandaram wrote:

>On the similar lines, I also think the XML support should turn itself
>OFF gracefully in environments that don't support XML. I think the patch
>requires JDK 1.4 or higher, so unless Derby has plans to end_of_line JDK
>1.3 (not sure if there is a plan), it may be a good idea to turn off XML
>internally. (Raise error when attempted to use)
>
>I plan to test this part and provide comments along with a few other items.
>
>Satheesh
>
>  
>
>>+1 on getting this initial XML support into Derby. Even though the patch
>>has already in, I will try to review the new version sometime.
>>At some point the testing does need to be part of the regular derby
>>suite though I think the current approach is good. I need to understand
>>the dependency on xerces, and if the default XML parser supplied by the
>>VM can be used instead.
>>
>>This is probably a good example of open source, get some initial working
>>functionality (incremental development) and then see if it can be
>>improved by others.
>>
>>Dan.
>>
>>
>>
>> 
>>
>>    
>>
>
>  
>

--Boundary_(ID_DhAJ/+lXeU+82pJOP4xMCA)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
At somepoint, it would be worthwhile to discuss which J2SE versions to
support.&nbsp; <br>
<br>
Satheesh Bandaram wrote:<br>
<blockquote cite="mid42A88D6E.2010808@Sourcery.Org" type="cite">
  <pre wrap="">On the similar lines, I also think the XML support should turn itself
OFF gracefully in environments that don't support XML. I think the patch
requires JDK 1.4 or higher, so unless Derby has plans to end_of_line JDK
1.3 (not sure if there is a plan), it may be a good idea to turn off XML
internally. (Raise error when attempted to use)

I plan to test this part and provide comments along with a few other items.

Satheesh

  </pre>
  <blockquote type="cite">
    <pre wrap="">+1 on getting this initial XML support into Derby. Even though the patch
has already in, I will try to review the new version sometime.
At some point the testing does need to be part of the regular derby
suite though I think the current approach is good. I need to understand
the dependency on xerces, and if the default XML parser supplied by the
VM can be used instead.

This is probably a good example of open source, get some initial working
functionality (incremental development) and then see if it can be
improved by others.

Dan.


    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
</body>
</html>

--Boundary_(ID_DhAJ/+lXeU+82pJOP4xMCA)--