[MonetDB-users] Schema Changes Through JDBC
I've been seeing some weird behavior when using Eclipse SQL Explorer to execute statements that modify the schema with the MonetDB May2009 release and the monetdb-1.10-jdbc.jar file. For instance, the statement CREATE TABLE Archive.Test ( var1 int, var2 varchar(100) ); yields a pop-up error message titled "Error Executing SQL" with the text "Schema statements are directly executed and therefor cannot be debugged, explained, profiled, traced, or used in a prepare statement". I'm not a Java user and haven't tried this in Java code as opposed to through SQL Explorer, so I can't conclusively link it to the JDBC driver as opposed to the SQL Explorer code, but I seem to recall this working in previous versions of MonetDB with SQL Explorer. Thoughts anyone? Is this supposed to work? Scott
On 21-06-2009 19:56:12 -0500, Scott Stephens wrote:
I've been seeing some weird behavior when using Eclipse SQL Explorer to execute statements that modify the schema with the MonetDB May2009 release and the monetdb-1.10-jdbc.jar file. For instance, the statement
CREATE TABLE Archive.Test ( var1 int, var2 varchar(100) );
yields a pop-up error message titled "Error Executing SQL" with the text "Schema statements are directly executed and therefor cannot be debugged, explained, profiled, traced, or used in a prepare statement".
I think the SQL explorer uses a prepared statement to execute all statements, which then fails for us. Personally, I think it is a limitation of MonetDB/SQL that schema statements cannot be prepared.
I'm not a Java user and haven't tried this in Java code as opposed to through SQL Explorer, so I can't conclusively link it to the JDBC driver as opposed to the SQL Explorer code, but I seem to recall this working in previous versions of MonetDB with SQL Explorer.
Thoughts anyone? Is this supposed to work?
participants (2)
-
Fabian Groffen -
Scott Stephens