[EMAIL PROTECTED] wrote:
Satheesh Bandaram <[EMAIL PROTECTED]> wrote on 14/04/2005 08:34:32 AM:
As Kathy Saunders announced in February, IBM is contributing attached Derby client to Apache Derby project. Derby client is a type 4 JDBC client driver that is designed to work with Derby NetworkServer.
<SNIP>
Can someone from IBM tell us what the status of the DB2 Universal Driver is with future versions of Cloudscape. Is it being replaced by the Derby Client?
The reason I ask is that in the past an application that could be used with Derby or Cloudscape 10 may have documented how to configure/use the DB2 Universal Driver. Should this documentation be changed to refer to the Derby client, or will future versions of Cloudscape continue to use the IBM DB2 Universal Driver for some reason and therefore we need to document both?
Thanks,
John
Hi,
It's currently my intention to continue supporting the DB2 Universal Driver for use with Derby (and Cloudscape) version 10.0. But, IBM will most likely move to the Derby client for Cloudscape in the future, and my vote would be that Derby uses the new client as well. If the Derby community votes to accept the new Derby client and it becomes part of the next release, I will probably only leave the existing DB2 Universal Driver available on the IBM developerWorks Cloudscape site for download for a while (for use with Derby 10.0); however, it will continue to be available as part of the DB2 product.
If the new client is adopted by Derby, then it seems to me the documentation should be changed for the next Derby release.
I won't make any final decisions regarding Cloudscape until Apache Derby has decided what to do.
Kathy (In case anyone is wondering, I'm the release manager for IBM Cloudscape)
