Bugs item #1739356, was opened at 2007-06-18 22:13 Message generated for change (Settings changed) made by mr-meltdown You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1739356&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/Core Group: SQL CVS Head >Status: Open Resolution: None >Priority: 7 Private: No Submitted By: bendeguz (bendeguz) Assigned to: Niels Nes (nielsnes) Summary: TRACE,PROFILE,DEBUG should be impossible for JDBC and ODBC Initial Comment: Dear MonetDB Developers, After my EXPLAIN bug report I have checked the TRACE, PROFILE,DEBUG availability for the JDBC client. The result is the same. Steps to reproduce: 1) Connect the database with mjclient 2) Issue the following queries: debug select count(*) from tables; trace select count(*) from tables; profile select count(*) from tables; Example scanario: monetdb-> debug select count(*) from tables; Error: protocol violation, unexpected line: mdb># mdb.start() monetdb-> trace select count(*) from tables; Error: protocol violation, unexpected line: breakpoint on select count(*) from tables; not set monetdb-> profile select count(*) from tables; Connection warning: mdb Symbol not found monetdb-> Regards, B. ---------------------------------------------------------------------- >Comment By: Fabian (mr-meltdown) Date: 2007-09-06 09:35 Message: Logged In: YES user_id=963970 Originator: NO nono. This is about JDBC and ODBC, which are application interfaces. The SQL server should make it technically IMPOSSIBLE to allow interactive stuff for such connections. IOW, only mclient should be allowed to access it. ---------------------------------------------------------------------- Comment By: Martin Kersten (mlkersten) Date: 2007-09-06 08:26 Message: Logged In: YES user_id=490798 Originator: NO This limitation has been added to the documentation. The role of mjclient has been reduced. The mjclient code could also trap SQL statements starting with these keywords and issue a warning. ---------------------------------------------------------------------- Comment By: Fabian (mr-meltdown) Date: 2007-07-16 20:05 Message: Logged In: YES user_id=963970 Originator: NO details: mdb is an interactive debugger that should never be started for an application like connection such as a JDBC connection. There is no way how JDBC can deal with an interactive debugger prompt. The interactive commands you described hence need to be disabled for JDBC connections. ---------------------------------------------------------------------- Comment By: Martin Kersten (mlkersten) Date: 2007-06-18 22:31 Message: Logged In: YES user_id=490798 Originator: NO Thanks for remarking this. Please use the C-version instead, i.e. mclient More details will follow. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1739356&group_id=56967 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Monetdb-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
