Bugs item #1739353, was opened at 2007-06-18 22:06 Message generated for change (Comment added) made by stmane You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1739353&group_id=56967
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: SQL/JDBC Group: Java "stable" Status: Open Resolution: Fixed Priority: 6 Private: No Submitted By: bendeguz (bendeguz) Assigned to: Fabian (mr-meltdown) Summary: EXPLAIN support from JDBC Initial Comment: Dear MonetDB Developers, The EXPLAIN query statement does not work from the JDBC client. The same query works from the command line client (mclient) Steps to reproduce: 1) Connect the database from a jdbc client (squirrelsql or mjclient) 2) issue the following query: explain select count(*) from tables; Check the result and the error message: a) Squirrelmail: Error: java.sql.SQLException: protocol violation, unexpected line: function user.s11_1():void;, SQL State: null, Error Code: 0 b) mjclient: Error: protocol violation, unexpected line: function user.s4_3():void; Regards, B. ---------------------------------------------------------------------- >Comment By: Stefan Manegold (stmane) Date: 2009-11-07 15:34 Message: Now that JDBC does (seem to) understand EXPLAIN (and PLAN, etc.), I added the stable output. Once testing confirms that it works fine on all platform, we can close this one. ---------------------------------------------------------------------- Comment By: Fabian (mr-meltdown) Date: 2009-08-14 09:35 Message: JDBC by itself does not understand any EXPLAIN stuff. What happens, is that the server sends the MAL code without any leading marker (!, #, [, ^, %) which upsets the MCL driver, which is very strict. IMO, EXPLAIN output should be a tuple result, e.g. all rows should be written as tuples ([ "blabla;" ]), or if that's easier, as XQuery rows (= blabla;), but a header should always be there. ---------------------------------------------------------------------- Comment By: Stefan Manegold (stmane) Date: 2009-08-13 14:30 Message: see http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker/explain.SF-1739353.out.00.html http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker/explain.SF-1739353.err.00.html ---------------------------------------------------------------------- Comment By: Stefan Manegold (stmane) Date: 2009-08-13 14:28 Message: re-opened as the test now fails with Error on line 1: protocol violation, unexpected line: function user.s1_1{autoCommit=true}():void; In case this is indeed the expected behavior, i.e., JDBC does not / no longer support EXPLAIN, then we should consider approving this error message in stable.err (and the empty stable.out). ---------------------------------------------------------------------- Comment By: Fabian (mr-meltdown) Date: 2007-07-17 13:13 Message: Logged In: YES user_id=963970 Originator: NO TEST ADDED - meltdown sql/src/test/BugTracker/Tests/explain.SF-1739353 ---------------------------------------------------------------------- Comment By: Stefan Manegold (stmane) Date: 2007-07-17 10:58 Message: Logged In: YES user_id=572415 Originator: NO Well, once EXPLAIN-support via JDBC is discontinued, the correct expected output for such test will be a proper error message ;-) ---------------------------------------------------------------------- Comment By: Fabian (mr-meltdown) Date: 2007-07-17 10:54 Message: Logged In: YES user_id=963970 Originator: NO yes, but it depends a bit on if EXPLAIN will be continued to be supported. ---------------------------------------------------------------------- Comment By: Stefan Manegold (stmane) Date: 2007-07-17 10:44 Message: Logged In: YES user_id=572415 Originator: NO Shouldn't we add a test for this one? A simple "explain select 1;" via JDBC might be enough ... ---------------------------------------------------------------------- Comment By: Fabian (mr-meltdown) Date: 2007-07-16 17:48 Message: Logged In: YES user_id=963970 Originator: NO Fixed in CVS, thanks! You need to update MonetDB5, clients and sql packages for this to work. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1739353&group_id=56967 ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Monetdb-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
