Implementation of ADOException indicating problems with communicating with the database (can also include incorrect ADO setup).

Collect data of an ADOException to be converted.

Implementation of ADOException indicating that the requested DML operation resulted in a violation of a defined integrity constraint.

Implementation of ADOException indicating that evaluation of the valid SQL statement against the given data resulted in some illegal operation, mismatched types or incorrect cardinality.

Implementation of ADOException indicating a problem acquiring lock on the database.

A factory for building SQLExceptionConverter instances.

Implementation of ADOException indicating that the SQL sent to the database server was invalid (syntax error, invalid object references, etc).

A SQLExceptionConverter implementation which performs no conversion of the underlying DbException. Interpretation of a SQL error based on DbException is not possible as using the ErrorCode (which is, however, vendor- specific). Use of a ErrorCode-based converter should be preferred approach for converting/interpreting SQLExceptions.

Knows how to extract a violated constraint name from an error message based on the fact that the constraint name is templated within the message.

The Configurable interface defines the contract for ISQLExceptionConverter impls that want to be configured prior to usage given the currently defined Hibernate properties.

Defines a contract for implementations that know how to convert a DbException into NHibernate's ADOException hierarchy.

Defines a contract for implementations that can extract the name of a violated constraint from a SQLException that is the result of that constraint violation.