[MonetDB-users] JDBC Driver Problem with the new Build..
HI All, We got the latest build and the JDBC Driver seems to be giving lot of problems.. When i try to view the tables for a given schema it doesn't show any even if there are tables. ( if i execute a select query it returns the results..) Also when i execute a query i am getting the following Error after the results.. [ERROR] Exception in ResultSet for "MYSCHEMA" java.sql.SQLException: Method not implemented yet, sorry! at nl.cwi.monetdb.jdbc.MonetResultSet.getCharacterStream(MonetResultSet.java:294) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.quantum.util.proxy.ProxyFactory$InvocationHandlerImpl.invoke(ProxyFactory.java:37) at $Proxy3.getCharacterStream(Unknown Source) at com.quantum.sql.SQLStandardResultSetResults.getStringFromCharacterSteam(SQLStandardResultSetResults.java:250) at com.quantum.sql.SQLStandardResultSetResults.parseResultSet(SQLStandardResultSetResults.java:147) at com.quantum.sql.SQLStandardResultSetResults.create(SQLStandardResultSetResults.java:69) at com.quantum.sql.MultiSQLServer.execute(MultiSQLServer.java:139) at com.quantum.sql.MultiSQLServer.execute(MultiSQLServer.java:91) at com.quantum.actions.BaseExecuteAction.getSQLResults(BaseExecuteAction.java:202) at com.quantum.actions.BaseExecuteAction.execute(BaseExecuteAction.java:174) at com.quantum.actions.ExecuteAction.execute(ExecuteAction.java:98) at com.quantum.actions.BaseExecuteAction.execute(BaseExecuteAction.java:125) at com.quantum.actions.BaseExecuteAction.run(BaseExecuteAction.java:111) at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:443) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443) at org.eclipse.equinox.launcher.Main.run(Main.java:1169) [/ERROR] thanks sateesh -- View this message in context: http://www.nabble.com/JDBC-Driver-Problem-with-the-new-Build..-tp15205660p15... Sent from the monetdb-users mailing list archive at Nabble.com.
Some additional data about this issue: MonetDB build was nightly=current (version 5.3.0) from 2008-01-30 JDBC driver was compiled on Sun JDK 1.5.0_7 Build and deployment on Linux 64bit (OpenSuse 10.1 / AMD Opteron) The same behaviour was found when the same version was built on 32 bit machine. We had been using version 5.2.2 without any problems with the JDBC driver, but had to move to 5.3.0 to take advantage of the fix for the SQL ALTER TABLE command when adding columns. We are running three mserver5 processes under 1 merovingian daemon. Using various SQL clients (SQuirrell SQL among others) we can connect to any of the three databases and see all the metadata for the databases and the schemas, but cannot get any listing of tables or access their content. sateesh wrote:
HI All,
We got the latest build and the JDBC Driver seems to be giving lot of problems..
When i try to view the tables for a given schema it doesn't show any even if there are tables. ( if i execute a select query it returns the results..)
Also when i execute a query i am getting the following Error after the results..
[ERROR] Exception in ResultSet for "MYSCHEMA" java.sql.SQLException: Method not implemented yet, sorry! at nl.cwi.monetdb.jdbc.MonetResultSet.getCharacterStream(MonetResultSet.java:294) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.quantum.util.proxy.ProxyFactory$InvocationHandlerImpl.invoke(ProxyFactory.java:37) at $Proxy3.getCharacterStream(Unknown Source) at com.quantum.sql.SQLStandardResultSetResults.getStringFromCharacterSteam(SQLStandardResultSetResults.java:250) at com.quantum.sql.SQLStandardResultSetResults.parseResultSet(SQLStandardResultSetResults.java:147) at com.quantum.sql.SQLStandardResultSetResults.create(SQLStandardResultSetResults.java:69) at com.quantum.sql.MultiSQLServer.execute(MultiSQLServer.java:139) at com.quantum.sql.MultiSQLServer.execute(MultiSQLServer.java:91) at com.quantum.actions.BaseExecuteAction.getSQLResults(BaseExecuteAction.java:202) at com.quantum.actions.BaseExecuteAction.execute(BaseExecuteAction.java:174) at com.quantum.actions.ExecuteAction.execute(ExecuteAction.java:98) at com.quantum.actions.BaseExecuteAction.execute(BaseExecuteAction.java:125) at com.quantum.actions.BaseExecuteAction.run(BaseExecuteAction.java:111) at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:443) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443) at org.eclipse.equinox.launcher.Main.run(Main.java:1169) [/ERROR]
thanks sateesh
-- View this message in context: http://www.nabble.com/JDBC-Driver-Problem-with-the-new-Build..-tp15205660p15... Sent from the monetdb-users mailing list archive at Nabble.com.
mmckennirey wrote:
Some additional data about this issue: MonetDB build was nightly=current (version 5.3.0) from 2008-01-30 JDBC driver was compiled on Sun JDK 1.5.0_7 Build and deployment on Linux 64bit (OpenSuse 10.1 / AMD Opteron)
The same behaviour was found when the same version was built on 32 bit machine.
We had been using version 5.2.2 without any problems with the JDBC driver, but had to move to 5.3.0 to take advantage of the fix for the SQL ALTER TABLE command when adding columns.
sateesh wrote:
[ERROR] Exception in ResultSet for "MYSCHEMA" java.sql.SQLException: Method not implemented yet, sorry! at nl.cwi.monetdb.jdbc.MonetResultSet.getCharacterStream(MonetResultSet.java:294)
JDBC hasn't changed in there for a very long time, so I wonder if the client utilities were somehow updated, or what changes in the server made the clients think that they now suddenly have to use a character stream. Maybe it is related to the column type of a table that you're trying to view. -- View this message in context: http://www.nabble.com/JDBC-Driver-Problem-with-the-new-Build..-tp15205660p15... Sent from the monetdb-users mailing list archive at Nabble.com.
participants (3)
-
Fabian2 -
mmckennirey -
sateesh