RE: [stellation-res] Stellation support for MySQL on Linux

["Jonathan Gossage" <jgossage@xxxxxxxx>]

> >-----Original Message-----
> >From: stellation-res-admin@xxxxxxxxxxxxxxx
> >[mailto:stellation-res-admin@xxxxxxxxxxxxxxx]On Behalf Of David Shields
> >Sent: November 2, 2002 9:28 AM
> >To: stellation-res@xxxxxxxxxxxxxxx
> >Subject: RE: [stellation-res] Stellation support for MySQL on Linux
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >> If that is the case than is not MySQL out of the question no
> >matter which
> >> JDBC driver we use? We have specific code in the database
> >support to deal
> >> with MySQL itself and that is definitely GPL. Does that not force the
> >> application og GPL irrespective of the JDBC library?
> >
> >We weren't aware of the problem when the code was added. The
> >change to GPL
> >for JDBC is only recent. The author now works for mysql.com
> >and the Connecctor J page tells you how to get non-GPL license, but that
> >doesn't
> >make any sense for an open-source project such as ours.
> >
> >
> >I'm very dubious about basing any of out future work on MySQL,
> >as it would
> >I think
> >require limiting ourselves to the LPGL version, thus giving up any chance
> >to exploit their future work. I'm also curious
> >what will happen when companies shipping proprietary code using
> >Connector J
> >will do when they
> >become aware of this change, but that's not our problem.
> >
> >> A little off topic, but relevant still. How do the CDT folks get away
> >with
> >> using GCC and its' toolchain which are all GPL licensed?
> >
> >They are just using the GCC for its intended purpose, not
> >incorporating it
> >in
> >their code. What I see as the problem with JDBC is that in using
> >it you are
> >bringing
> >bytes based on its source into memory, which can be viewed as
> >"loading" and
> >that
> >brings you under the GPL. There are also specific exemptions re use of
> >libraries
> >for GPL code under Linux and Cygwin under Windows, but I doubt they apply
> >to JDBC's and on Windows when
> >not using Cygwin (and I do *not* want to take the Cygwin route
> >on Windows).

I have to agree with you there. Although Cygwin is not that hard to install
under Windows, it puts a potentially large chunk of code on a machine that
the user might not, otherwise have any use for. It also could be a
deployment hassle in a commercial shop where users do not control their own
machines. This happens even to developers in some places!

I guess the bottom line is that unless a a CPL compatible JDBC driver
becomes available that we could distribute we are out of luck with MySQL.
Which leaves the problem of an open source database for Windows. The current
Postgres installs and works fine under Windows providing you install two
additional components, namely Cygwin and the Cygipc package which provides
Unix System V IPC mechanisms. This latter package is in he process of being
folded into the standard Cygwin DLL but this process is not yet complete. I
have yet to try Firebird but I think I should raise its' priority given the
MySQL situation.
> >
> >dave
> >

Regards

Jonathan

Personal Email
jgossage@xxxxxxxx

Business Email
jonathan@xxxxxxxxxxxxxx