I like this idea. If you want to provide meaning to getSQLState I think
you have to look at the SQLState values and provide a mapping from isc
error codes to them.

It would also be _very_ good if you could discern which problems meant the
connection was unusable and send a ConnectionErrorOccurred message through
the ConnectionEventListeners.

Thanks
david jencks

On 2002.05.30 08:23:56 -0400 Ken Richard wrote:
> I would like to enhance the exception handling code in the driver.
> Currently, SQLExceptions are usually created with code like:
>
> catch (GDSException ge)
> {
> log.info("GDSException in PreparedStatement constructor",
> ge);
> throw new SQLException("GDSException: " + ge);
> } // end of try-catch
>
> How about creating a FBSQLException that extends SQLException. The
> exception would support the getErrorCode to get the native error number
> and support getNextException to return the original GDSException.
>
> Question: what should be returned from getSQLState?
>
>
>
>
> To unsubscribe from this group, send an email to:
> Firebird-Java-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>
>