db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <Richard.Hille...@Sun.COM>
Subject Re: drda datatypes
Date Mon, 15 Aug 2005 19:39:44 GMT
Hi Kathey,

I'm happy to pursue this if you want to share your contact's contact 
info. Of course, you may have special pull with this contact and so may 
want to pursue this yourself.


Francois Orsini wrote:

>I think it's worth investigating option #1 to try and get some idea of
>when these types could be added - getting in touch with Open Group and
>start some dialogue (Kathey seems to have a contact) - Option #2 could
>be done in parallel IMO...just some thoughts...
>Now if the current DRDA client driver is used to communicate with a
>data source different than Derby and the application is making use of
>these non-officially supported types, this case would have to be
>On 8/15/05, Rick Hillegas <Richard.Hillegas@sun.com> 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:
>>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.

View raw message