Date: 2015-06-27 18:20:24 +0200
From: Alexander Alexandrov <<alexander.alexandrov>>
To: clients devs <>
Version: 11.19.15 (Oct2014-SP4)
CC: @hannesmuehleisen

Last updated: 2015-08-28 13:41:45 +0200

Comment 20945

Date: 2015-06-27 18:20:24 +0200
From: Alexander Alexandrov <<alexander.alexandrov>>

User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:

The MonetDB JDBC driver currently has to be manually loaded by the client via Class.forName(...) prior to usage.

According to the DriverManager documentation [1], the driver can be added automatically by the JVM if one adds a META-INF/services/java.sql.Driver file to the jar containing the fully qualified class name of the SQLDriver implementation.

[1] https://docs.oracle.com/javase/7/docs/api/java/sql/DriverManager.html

Reproducible: Always

Steps to Reproduce:

1. Run DriverManager.getConnection("jdbc:monetdb:...") without calling Class.forName(...) first.

Actual Results:

Throws a "No suitable driver found for jdbc:monetdb:..." error.

Expected Results:

The driver should be discovered automatically if the jar is in the runtime classpath.

Comment 20963

Date: 2015-07-03 12:56:22 +0200
From: @hannesmuehleisen

Fixed in rev. 51565d00c2c5

Comment 21001

Date: 2015-07-15 14:10:11 +0200
From: MonetDB Mercurial Repository <>

Changeset 9dc80e4dacbd made by Hannes Muehleisen hannes@cwi.nl in the MonetDB repo, refers to this bug.

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

Changeset description:

Java Client: Fix for Bug #3748
(grafted from 51565d00c2c54d68447c8d97017b64777329a441)

Comment 21185

Date: 2015-08-28 13:41:45 +0200
From: @sjoerdmullender

Jul2015 has been released.