You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Sunitha Kambhampati <ks...@gmail.com> on 2006/09/02 08:16:32 UTC

Info provided in SQLException & ExceptionSeverity.

I was reviewing the dev guide and in 
http://db.apache.org/derby/docs/10.2/devguide/cdevconcepts844813.html
pg63: Section 'Information provided in SQLExceptions" there is

"Use the /getSQLState/ and /getMessage/ methods to view the /SQLState/ 
and error messages.
 Use /getErrorCode/ to see the error code. The error code defines the 
severity of the error and is not unique to each exception.
 The severity levels are described 
in/org.apache.derby.types.ExceptionSeverity/."

In another thread (derby-1566), Dan pointed out that  "The severity by 
definition (SQLException.getErrorCode) is a non-standard piece of Derby. "

So, it seems that :
-- Might be good to  add this piece of information  that severity is  
non-standard and also encourage applications to not depend on severity
-- Remove mention of internal class ExceptionSeverity here because it is 
not exposed api and   I dont see this in  the javadoc
http://db.apache.org/derby/javadoc/publishedapi/jdbc4/  .Also, that 
package name for ExceptionSeverity is incorrect, this is actually 
org.apache.derby.common.error.ExceptionSeverity

Is this reasonable ?

Thanks,
Sunitha.