db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Hlavatý <hla...@code.cz>
Subject JDBC driver for Derby network server mode?
Date Sat, 28 Aug 2004 01:49:59 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We may have a problem with JDBC driver.
Or, more precisely, we don't have a JDBC driver for networked server configuration of Derby
;(
http://incubator.apache.org/derby/manuals/getstart/gspr36.html states we have to use JDBC
driver
from IBM DB2, without providing exact pointers, or license information. That was OK for IBM's
Cloudscape,
but how about Derby?

Can someone please explain the situation? I feel a bit funny about it...

We need to know / find out:

- - Where the JDBC driver is (i guess its hidden inside DB2 distribution)
- - Under what conditions it can be used (can we at all? Can we provide it as a separate download?)

If we can use the driver, we need a clear permission/license from IBM for unlimited production
use and a separate download page for the JDBC driver for Derby users to download from (or
permission
to redistrubute on Derby site).

If we can't use the driver - heck, we better start working on our own DRDAv3 protocol based
one ;-)
As bad as it would be, on the bright side it would allow us to improve the driver and fix
bugs ;)
(Yikes! the DRDAv3 spec has 700+ pages ;( )

The funniest outcome would be for IBM to opensource its universal JDBC driver too,
but that's not very probable ;-)

Can someone responsible from IBM enlighten us on the issue please?

Jan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQEVAwUBQS/kx3FDePgyse5HAQJ77Qf+KsqJosfn9SPs3kjTfe0lRphuNIfLqChU
QuUFFXISjrFGl7nBK2QRFpj1iheb8buoZyBUJTBMdYzME2e/1Of3waRxD3FM1H/w
yXHDoR9T+L4JyV2h9lNhcAtkCA6x4Lh9h5fNR0KkuiC7ZXvGuAQXLRciZJceMk1l
YebYYecz7rVQrg7FZmQ3vnfa5W5YQHK6oMAvqXJQFgiUqjPJA7hGbXpBrrB+hecV
nUeW/vezaPFhNW/eP6R5xjFnPRw+s7HyGvWRBZ2HfNaJ785vWMW8w/MT/i4+Fwdn
yyC2EmS0M11ZQ2p3qe0eSv6Cp2ebN1BkqwSIGD7LTGtAXDYal+rGEA==
=GCnU
-----END PGP SIGNATURE-----

Mime
View raw message