[EMAIL PROTECTED] wrote:

> Author: davidvc
> Date: Wed Jan 25 07:25:08 2006
> New Revision: 372240
> 
> URL: http://svn.apache.org/viewcvs?rev=372240&view=rev
> Log:
> DERBY-400: Fixed the SQLState for some of the new client messages
> to better match what is required by SQL2003

> +# 0A - Feature not supported
> +0A002.S=jdbc 2 method is not yet implemented.
> +0A003.S=JDBC 3 method called - not yet supported

0A003 is not valid SQLstate. You need to use 0A000 or some other 0Axxx
value where the xxx is not in the range reserved by the standard (as
003) is.

I actually don't see a need for multiple error messages in this case.
Does any caller really care that it's a JDBC 2 vs. JBDC 3 method.

Dan.

Reply via email to