jConnect provides an EedInfo interface that specifies methods for obtaining Sybase-specific error information. The EedInfo interface is implemented in SybSQLException and SybSQLWarning, which extend the SQLException and SQLWarning classes.
SybSQLException and SybSQLWarning contain the following methods:
public ResultSet getEedParams( );
Returns a one-row result set containing any parameter values that accompany the error message.
public int getStatus( );
Returns a “1” if there are parameter values, returns a “0” if there are no parameter values in the message.
public int getLineNumber( );
Returns the line number of the stored procedure or query that caused the error message.
public String getProcedureName( );
Returns the name of the procedure that caused the error message.
public String getServerName( );
Returns the name of the server that generated the message.
public int getSeverity( );
Returns the severity of the error message.
public int getState( );
Returns information about the internal source of the error message in the server. For use by Sybase Technical Support only.
public int getTranState( );
Returns one of the following transaction states:
0 The connection is currently in an extended transaction.
1 The previous transaction committed successfully.
3 The previous transaction aborted.
Some error messages may be SQLException or SQLWarning messages, without being SybSQLException or SybSQLWarning messages. Your application should check the type of exception it is handling before it downcasts to SybSQLException or SybSQLWarning.
| Copyright © 2003. Sybase Inc. All rights reserved. |
|
|
