Documentation

The top-level error class. Errors in MSSQL are divided into different classes, which are further subdivided into individual error subclasses. It is useful to determine the class of database exception and handle it appropriately.

Assign each error class' subclasses an appropriate API error code

Parsing error class and subclass information from a SQLSTATE code. SQLSTATE provides detailed information about the cause of a warning or error. A SQLSTATE consists of 5 chars. They are divided into two parts: the first and second chars contain a class and the following three a subclass.

A default transaction error handler where all errors are unexpected.

A transaction error handler to be used in constructing mutation transactions, i.e INSERT, UPDATE and DELETE. We expect data exception and integrity constraint violation.

Constructs a transaction error handler given a predicate that determines which error classes (and subclasses) are expected and should be reported to the user. All other errors are considered internal errors. Example:- Consider a insert mutation where we insert some data into columns of a table. Except for the basic data type, such as Boolean, String, Float, Int etc. we cannot invalidate data any further, such as validating timestamp string format. In this case, a @DataException is expected from the database and it is handled and thrown with proper error message.

The ODBCException type has no ToJSON instance. This is an attempt to convert the odbc exception to a JSON @Value