Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update JDBC driver to JDBC4 #2802

monetdb-team opened this issue Nov 30, 2020 · 0 comments

update JDBC driver to JDBC4 #2802

monetdb-team opened this issue Nov 30, 2020 · 0 comments


Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2011-04-07 08:43:24 +0200
From: @grobian
To: clients devs <>
Version: 11.5.3 (Aug2011-SP1) [obsolete]
CC: charnik, gburd

Last updated: 2012-01-26 15:31:59 +0100

Comment 15728

Date: 2011-04-07 08:43:24 +0200
From: @grobian

Since Java SE 5 is EOL, and the preferred/default Java EE is also 6 these days, our JDBC driver should be updated from JDBC3 to JDBC4. We can safely require Java 6, as that is the current version which often is the only version available.

We can ignore compatability with JDBC3 (Java 5), as this only excludes PowerPC based Mac OS X system, which are close to extinct as Java 5 is.

Comment 16432

Date: 2011-10-14 14:42:52 +0200
From: @grobian

Changeset 49596fdde953 made by Fabian Groffen in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=49596fdde953

Changeset description:

jdbc: implement changes necessary for JDBC4

JDBC4 was introduced with Java 6.  Adding support for this was long
overdue, since Java 5 has reached its EOL for a while now.  We decided
not to add any backwards compatible Java 5 code path, since Java 5
should be close to extinct.  See bug #2802.

Comment 16821

Date: 2012-01-26 15:31:59 +0100
From: @sjoerdmullender

The Dec2011 version has been release, so declaring this bug as FIXED.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant