Re: Is this a bug ?
Posted by: R Lenard
Date: December 21, 2004 07:12PM

Mark Matthews wrote:
> R Lenard wrote:
> > Mark Matthews wrote:
> > > > This is with mysql-4.1.7 and
> > > connectorj-3.0.16
> > > >
> > > > Any ideas ?
> > > >
> > >
> > > A couple...First, why aren't you using
> > Connector/J
> > > 3.1.x with MySQL-4.1.x? If you're using
> the
> > newest
> > > MySQL server, and want to use all of
> it's
> > > features, and have the latest bug fixes,
> then
> > you
> > > should be using the latest version of
> the
> > JDBC
> > > driver as well.

It turns out by adding this to the URL the problem is solved !!

connectTimeout=20000&useUnbufferedInput=false


> >
> > Because Connector/J 3.1.x is not GA - so
> surely GA
> > versions are compatible with each other ...
>
> In this case, not really. The connectors that
> aren't based on libmysql (.Net, JDBC) always lag
> the server's GA release by a month or so, as we
> have to re-implement things that any
> libmysql-based client already gets 'free'. When
> the server first goes 'ga', there's a flurry of
> bug-fixes that usually end up with changes that
> are better left to 'settle' before any of the
> other connectors can implement them.

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 ??

> >
> > There's no way (unless I was the developer of
> the
> > server) for me to know what the problem is.
> Sure
> > some things are obvious, but alot aren't.
> > Presumably some of the errors are
> unrecoverable ?
> > Or there is a reasonable workaround ...
>
> Are you asking for a 'workaround' table for each
> of the errors listed there? If so, I'll have to
> talk to the docs team...because it should exist
> for the entire server...It's also a monumental
> undertaking. Aside from this one, many of the
> errors that would be non-obvious to the end-user
> come from failures in hardware and/or operating
> system and could be any one of tens of reasons,
> sometimes with no workarounds.

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

Options: ReplyQuote


Subject
Written By
Posted
December 19, 2004 09:22PM
December 20, 2004 03:27PM
December 20, 2004 03:42PM
December 20, 2004 05:13PM
Re: Is this a bug ?
December 21, 2004 07:12PM
December 21, 2004 07:52PM
December 21, 2004 09:32PM
December 21, 2004 09:43PM
December 21, 2004 10:13PM
December 21, 2004 10:28PM
December 21, 2004 11:38PM
December 21, 2004 11:45PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.