JDBC: Incorrect behaviour when the Exasol driver is tested against a non-Exasol database
Details
| Detail name | Value |
|---|---|
| Changelog Number | 13049 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | |
| Fix Versions | Exasol 7.1.2 |
| Resolution Date | 2021-10-20 |
Background
A driver manager connects to a database by sequentially trying all registered database drivers. The driver manager expects each incorrect driver to return a null-pointer.
If connecting to a non-Exasol database with the Exasol JDBC driver, a null-pointer is the correct behavior.
Description
In some cases when connecting to a non-Exasol database with the Exasol JDBC driver, a fingerprint error message is raised instead of the expected null-pointer.
[ERROR] More than one fingerprint was provided.
Workaround
There is no workaround.
Fix
If the Exasol JDBC driver is used to connect to a non Exasol database, a null-pointer exception is always raised.
