Folks
Is there any standard for the ordering of nested SQLExceptions ?
Looking at the setNextException() source, this adds the new exception to the end of the chain - thus inferring that the first SQLException in the chain details the root cause of the problem.
However, in reality, the SQLExceptions we get back from our Informix 2000 DBMS via Informix's own type 4
JDBC driver have the meat of the exception at the end of the chain - thus inferring that the last SQLException in the chain details the root cause of the problem.
I cannot find any documentation that gives an official stance on this; if, indeed, there is one.
Regards
Gary