Hi Fabian, the command line example still uses the -b switch to select the database which results in an unknown argument error. Cheers, Viktor Fabian Groffen wrote:

Hi Viktor,

On 28-11-2011 12:48:43 +0100, Viktor Rosenfeld wrote:

...

the example at the top of the documentation of the JDBC client at http://www.monetdb.org/Documentation/Cookbooks/SQLrecipies/Clients/JDBC uses the -d switch to specify the table and the -b switch to specify the database. However the current version does not recognize the -b switch and the -d switch can be used to select the database as is documented further on the page.

Also, the page says that TRACE is not possible via JDBC. However, as the jdbcclient.jar demonstrates it is indeed possible to use TRACE on a query by checking additional result sets.

Thanks, I've updated the page.

------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d

_______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users

Hi Fabian, Fabian Groffen wrote:

On 28-11-2011 18:47:55 +0100, Viktor Rosenfeld wrote:

...

Hi Fabian,

the command line example still uses the -b switch to select the database which results in an unknown argument error.

I'm not too compatible with the editing interface the website gives me... thanks for coming back on this. Should be fixed now.

Looks good now.

Just a word of warning here, jdbcclient is no longer supported and should only be used for testing basic JDBC interaction. mclient has superseeded jdbcclient in all possible dimensions.

Thanks for the tip. It was useful enough to figure out how to get the MAL trace over JDBC. Cheers, Viktor