db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kim Haase <Camilla.Ha...@Sun.COM>
Subject Re: When and why use DB2UDB jdbc driver instead of the Derby ClientDriver to access a DERBY NETWORK SERVER?
Date Mon, 04 Aug 2008 19:19:32 GMT
Rick Hillegas wrote:
> Kim Haase wrote:
>> Kathey Marsden wrote:
>>> Alan Burlison wrote:
>>>> Related question:  If you want to connect to a Derby instance using 
>>>> something other than Java (C, Python Perl etc), what's the 
>>>> recommended mechanism?  Google suggests the DB2 driver, but most of 
>>>> the articles and howto's are several years old, and date back to the 
>>>> Cloudscape days.
>>> Hi Alan,
>>> IBM no longer provides support for the DB2 driver with Derby  and is 
>>> not testing it with new releases. It would be great to see an open 
>>> source initiative for an ODBC driver for Derby.  Although this is 
>>> often requested, I don't think we have a Jira entry for it yet.  
>>> Perhaps you could open one.
>> There are a couple of topics on the DB2 driver in the Derby 
>> Administration Guide. Should these be removed, do you think? If so, I 
>> could file a JIRA issue for this. Possibly we should just add a note 
>> about the lack of support?
>> Thanks,
>> Kim Haase
> If the driver is no longer supported and isn't being tested against new 
> Derby releases, then it makes sense to me to remove references from the 
> Derby user manuals. Maybe the information could migrate to the wiki 
> along with a note stating that the DB2 driver is not supported or tested 
> anymore.
> Regards,
> -Rick

Thanks for the suggestion, Rick. I can file an issue to remove the info 
from the docs. I'm not so familiar with the wiki, so I'm not quite sure 
where to move it to --

  - The JDBCSupport page? How up to date is this (it predates JDBC 4)?
  - HintsAndTips?
  - UsesOfDerby?


View raw message