IBProvider v2.1. The error processing mechanism is completely reconstructed

The error processing mechanism is completely reconstructed. Now [IBProvider can use OLE DB services to create more detailed description of occurred errors:

• Error collections. Earlier several errors were united into one, which could lead to displaying a very long error message.
• Error parametrization. Earlier the only information, that could be obtained from the object of error, was text description. Now you can get more detailed error description. It is an error code (specific for IBProvider) and parameters. For more details see IErrorRecords interface description.

Since ADO.NET can process only OLE DB errors, from now IBProvider completely satisfies these requirements.

Technical details

• Error processing is completely based on C++ exceptions. Pay attention that when debugging your applications, debugger can react to the exceptions inside the provider.
• There is a limitation in the provider to a maximum quantity of errors returned in error collection. Due to this a generation of the potentially long errors lists is avoided when such operations as delayed commit in updatable rowsets.

Preferences

• Simplification and cardinal improvement of the provider internal structure.
• General productivity is improved. In particular several fairly complicated error control constructions were removed from data selection operation (fetch).
• Sufficiently significant decrease in size of the provider optimized build.
• Basis for further localization of error messages appeared.

If OLE DB services (forming part of ADODB) are not installed on computer, then the provider will use a standard mechanism of error processing with the use OLE Automation.

New error processing is implemented for both versions of the IBProvider — 1.7.14 and 2.1.