Lance J. Andersen wrote:
Kathey Marsden wrote:
There was a discussion started in DERBY-401 on this but I thought I
would submit it as a separate thread. The JDBC 4.0 spec says in
section 8.5.1..
A NonTransient SQLException must extend the class
SQLNonTransientException. A NonTransient
Kathey Marsden wrote:
Lance J. Andersen wrote:
Kathey Marsden wrote:
There was a discussion started in DERBY-401 on this but I thought I
would submit it as a separate thread. The JDBC 4.0 spec says in
section 8.5.1..
A NonTransient SQLException must extend the class
Kathey Marsden wrote:
Lance J. Andersen wrote:
Kathey Marsden wrote:
There was a discussion started in DERBY-401 on this but I thought I
would submit it as a separate thread. The JDBC 4.0 spec says in
section 8.5.1..
A NonTransient SQLException must extend the class
Kathey Marsden wrote:
There was a discussion started in DERBY-401 on this but I thought I
would submit it as a separate thread. The JDBC 4.0 spec says in
section 8.5.1..
A NonTransient SQLException must extend the class
SQLNonTransientException. A NonTransient SQLException would be thrown
Lance J. Andersen wrote:
perhaps it is worth going back to DRDA and asking them where/how they
came up with that class value?
I put a query into the one DRDA contact I have but unfortunately he is
out for a few weeks. Perhaps Rick knows someone who could answer where
class 58 came from.
Kathey Marsden wrote:
Lance J. Andersen wrote:
perhaps it is worth going back to DRDA and asking them where/how they
came up with that class value?
I put a query into the one DRDA contact I have but unfortunately he is
out for a few weeks. Perhaps Rick knows someone who could answer where
Daniel John Debrunner wrote:
Kathey Marsden wrote:
Lance J. Andersen wrote:
perhaps it is worth going back to DRDA and asking them where/how
they came up with that class value?
I put a query into the one DRDA contact I have but unfortunately he
is out for a few weeks. Perhaps Rick knows
Yes, I see that now on a second pass at section 23.
However, to answer Kathy's question, no, the SQL Class Values used for
JDBC SQLExceptions were defined around the standard SQL class values,
not implementation defined class values. Perhaps we can consider
extending this in JDBC 4.1, but
The XS and XB errors come from the old scheme where severity was totally
expected to be handled by the x.SEVERITY system. On quick scan they
are mostly not expected to happen errors marked session level. Can we
just wrap any session level severity error into an 08 number (maybe
chain is
