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 (asf.osuosl.org: local policy)
Date: Mon, 15 Aug 2005 11:46:20 -0700
From: David Van Couvering <David.Vancouvering@Sun.COM>
Subject: Re: drda datatypes
In-reply-to: <4300E1A8.9040303@sun.com>
To: Derby Development <derby-dev@db.apache.org>
Message-id: <4300E2FC.7020007@sun.com>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_1X60XVst6RVuuahju1Bnxw)"
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
References: <4300E1A8.9040303@sun.com>

This is a multi-part message in MIME format.

--Boundary_(ID_1X60XVst6RVuuahju1Bnxw)
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT

I vote for option 2, as long as we provide backward compatibility with 
clients running at earlier versions of 10.x.  Option 3 seems a bit drastic.

David

Rick Hillegas wrote:

> According to the January 2004 rev of the DRDA spec, DRDA does not 
> support the following SQL datatypes which we want to support or 
> already partially support:
>
> BOOLEAN
> NCHAR
> NCLOB
> NVARCHAR
> SQLXML
>
> How do we move forward to support these types? Here are some 
> suggestions. What do you think?
>
> 1) Wait until the spec owner (Open Group) adds these to a future rev 
> of DRDA. We would lobby Open Group to do this.
>
> 2) Create our own, custom-rev of DRDA which supports these datatypes. 
> Jim Gray seems to think that the spirit of DRDA allows these 
> customizations (see the following paper: 
> research.microsoft.com/~gray/papers/SqlAccessVsDrda.doc ). In this 
> scheme, Derby 10.2 clients and servers would ship with support for the 
> new datatypes. 10.2 servers would have to do something creative when 
> 10.1 or db2jcc clients accessed these datatypes.
>
> 3) Support some other data interchange format, either alongside or in 
> place of DRDA.
>
> -Rick
>
>
>

--Boundary_(ID_1X60XVst6RVuuahju1Bnxw)
Content-type: text/x-vcard; charset=utf-8; name=david.vancouvering.vcf
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=david.vancouvering.vcf

begin:vcard
fn:David Van Couvering
n:Van Couvering;David
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:david.vancouvering@sun.com
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard


--Boundary_(ID_1X60XVst6RVuuahju1Bnxw)--