db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@apache.org>
Subject Re: Multiple causes for same SQL State
Date Wed, 25 Jan 2006 01:15:06 GMT
David W. Van Couvering wrote:

> I have noticed that there can be multiple exceptions that can map to the
> same standard SQL State.  For example, 08003 means "connection does not
> exist".  I have found at least two places where this is valid.
> I think it's reasonable to do something like this in SQLState.java
> String CONN_ERROR_1 = "08003.C.1";
> String CONN_ERROR_2 = "08003.C.2";
> The code that extracts severity from the message id would not be
> impacted, as it only looks at the 7th character.
> This seems reasonable to me, but looks like a break from what has been
> done in the past.  Is there anything I'm missing that I should be aware
> of before I take this approach?

I think this approach is already taken for a few errors in the embedded


View raw message