Date: 2015-10-16 07:46:17 +0200
From: Vijay Krishna <>
To: clients devs <>
Version: 11.19.15 (Oct2014-SP4)

Last updated: 2015-11-19 12:30:57 +0100

Comment 21341

Date: 2015-10-16 07:46:17 +0200
From: Vijay Krishna <>

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36
Build Identifier:

I am trying to connect a schema within a database directly through JDBC with the following Java code.

Connection con = DriverManager.getConnection("jdbc:monetdb://localhost/testDB", "monetdb", "monetdb");
con.setSchema("schema1");

But this throws the following exception.
Exception in thread "main" java.sql.SQLException: syntax error, unexpected '=' in: "set schema ="
at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.executeQuery(MonetConnection.java:2525)
at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.processQuery(MonetConnection.java:2273)
at nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:497)
at nl.cwi.monetdb.jdbc.MonetStatement.execute(MonetStatement.java:338)
at nl.cwi.monetdb.jdbc.MonetStatement.executeUpdate(MonetStatement.java:533)
at nl.cwi.monetdb.jdbc.MonetConnection.setSchema(MonetConnection.java:1267)
at batcave.Monet.main(Monet.java:11)

Reproducible: Always

Steps to Reproduce:

1.Try to connect mclient through JDBC interfaces with the above code.
2.
3.

Actual Results:

The above mentioned exception is thrown

Expected Results:

Successful JDBC DB Connection to the specified schema

Comment 21343

Date: 2015-10-16 09:15:29 +0200
From: MonetDB Mercurial Repository <>

Changeset 0f9c3b647c5a made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.

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

Changeset description:

Fix syntax in JDBC setSchema method.
This fixes bug #3823.

Comment 21447

Date: 2015-11-03 10:18:34 +0100
From: @sjoerdmullender

Jul2015 SP1 has been released.

Comment 21557

Date: 2015-11-19 12:30:57 +0100
From: Vijay Krishna <>

Hi, Is this issue fixed? I could reproduce the same in monetdb-jdbc-2.18.jar

Since the status was changed to Resolved before the above jar's release, I tested this with it.

If its set for next release, can we have the status changed as NEXTRELEASE ??