R Lenard wrote:
> Give that this isn't documented on the JDBC
> documentation or the downloads and the website
> implies that the 3.1.x version is quite a way from
> "production"(See
>
http://www.mysql.com/products/connector/j/ - it
> talks about "the development version is being
> refactored") how is anyone meant to realise this
> ??
Sorry, the website text is an oversight, it should've been updated.
We'll update the docs as well to point out what's going on with respect to what version you should use with what version of the server.
If you're not subscribed to the
java@lists.mysql.com mailing list, you should be, as announcements about all JDBC driver releases end up there, with helpful text such as this in them:
"MySQL Connector/J 3.1.5, a new version of the Type-IV all-Java JDBC
driver for MySQL, has been released.
Version 3.1.5 is the first and only planned GAMMA release
of the 3.1 series that is suitable for use with any current or
development version of MySQL (e.g. 3.23, 4.0, 4.1 or 5.0).
This version of Connector/J is required to use server-side prepared
statements with MySQL-4.1 or invoke stored procecdures or retrieve view
metadata with MySQL-5.0.
If no fatal bugs are found with 3.1.5 in the next few weeks, Connector/J
3.1.6 should be released as a generally available/production build
before the winter holidays."
> Ideally - yes. But sure many are not possible.
> However there are some that it definitely makes
> sense to describe more and there are some
> important cases that should to be done - like the
> "UNKNOWN COMMAND".
>
> > In any case, 'UNKNOWN COMMAND' usually means
> that
> > you have a bug in the driver, or you have a
> > version mis-match between your client and
> the
> > server.
>
> Looks like a bug in the driver as it turns out by
> adding this to the URL the problem is solved !!
>
> connectTimeout=20000&useUnbufferedInput=false
What happens if you use Connector/J 3.1.5 _without_ _any_ options?