Alan Burlison wrote:
> Stanley Bradbury wrote:
>
>> With release 10.0 of Derby there was no open source client driver so
>> the DB2 driver was required to use Network Server. With Derby 10.1
>> the Derby Client driver was introduced and the recommendation made
>> everyone use that client driver. This remains true today.
>
> 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.
>
> I've been using Derby very happily for the development stage of my
> project, but I'm probably going to have to switch to MySQL unless I
> can get decent connectivity to Derby from other languages, in
> particular from scripting languages.
>
I am only aware of the following JDBC-ODBC solutions that are listed on
the Derby Wiki (in addition to the DB2 UDB CLI based one) at:
http://wiki.apache.org/db-derby/UsesOfDerby?highlight=%28odbc%29#head-df9797cbbfc50b7990efd862bb7779b92df9d087
Carob
EasySoft ODBC-JDBC Gateway
OpenDRDA
|