Re: Is this a bug ?

[Mark Matthews]

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

>
> > > This is one part of the documentation
> that
> > is
> > > sadly lacking - exception / error
> handling..
> > >
> >
> > Hmm...there's a _whole_ multipage table in
> the
> > docs that tells you what error conditions on
> the
> > server will throw what SQLExceptions with
> given
> > SQLStates...However 'unknown command'
> usually
> > means something more serious is goofed up,
> like
> > your network connection is flaky or you have
> a bad
> > server build....as what the server is
> receiving is
> > not what it expects.
>
> No offence intended, but I wouldn't have made the
> comment unless the multipage table was lacking..
> For instance what is this ?
> 1047 ER_UNKNOWN_COM_ERROR 08S01 HY000
>
> 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.

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.