Hi Fernand,
> Make a choice between the driver you want to use, because : wath > works > for JDBC not alwais works for ODBC etc.... Yes, I know, or rather have learnt the hard way, but this shouldn't be the case...The problem with using JDBC is the performance factor, because it is far, far slower than ODBC when using OOo and always has been. I still get "Nested Exception" messages due to connection timeouts using the JDBC connector over a remote connection to the my mysql server, which quite frankly sucks big time. I know that there is a parameter you can pass the JDBC driver to reconnect automatically, but if you read the MySQL documentation, they advise you not to use it as it was only meant to be used to maintain backwards compatibility with older server versions. Hence my preference for ODBC. It is a no win situation :-( > > When using Functions who are server specific like (MONTHNAME) then you > > need to past native SQL and hopes that the driver support this > functions Not all functions are suported by every driver, if not then > > trye a driver specific function. Hmm, the difficulty is knowing which functions work with which driver... > problem2: > Parameters are working but you must past them as NON-native SQL :-) > and > formulate then as *like :myinput* (no space between the ":" and > "myinput") > Thanks, I will try that out, but I didn't realise you had to use the LIKE operand, this doesn't appear to be referenced in the MySQL official documentation (unless I've looked in the wrong place). > > ps: why not trying the native SQLconnector ? The native connector doesn't yet work with ports other than the default 3306 :-(( which is how I'm accessing the mysql server. The fix has been done, but obviously will have to wait for the next release of the connector to be integrated. Thanks for your hints, Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
