Fixed incorrect error messages for invalid connection string syntax in Exasol ODBC driver

Detail name	Value
Changelog Number	15363
Type	Improvement
Status	Resolved
Fix Versions	Exasol 8.33.0, ODBC 25.2.1
Resolution Date	2025-02-26

Description

The Exasol ODBC driver has been updated to properly handle cases where the connection string contains invalid syntax. Previously, the driver did not recognize invalid syntax and produced incorrect error messages upon connection failure.

Previous Behavior:

When the connection string contained invalid syntax, the driver produced misleading error messages, making it difficult for the user to diagnose and fix the issue.

Example

EXAHOST = jdbc:exa:127.0.0.1:8563

[08S01][unixODBC][EXASOL][Exasol driver]Failed to resolve hostname: 'jdbc'.
[ISQL]ERROR: Could not SQLConnect

New Behavior:

The driver will now recognize and properly handle invalid syntax in the connection string, providing a clear and correct error message.

Example

EXAHOST = jdbc:exa:127.0.0.1:8563

[S1000][unixODBC][EXASOL][Exasol driver]Syntax error found in connection string.

Database version 8.33.0 contains this new version of ODBC / Client SDK driver, therefore validity check of connection string in IMPORT/EXPORT FROM/TO EXA will be stricter. In particular, IMPORT/EXPORT FROM/TO EXA from a 'jdbc:exa:<something>` won't be possible anymore (it shouldn't have ever worked).

Fix

• The driver will now correctly identify and report an invalid connection string syntax.
• If the connection string’s format is invalid, the driver will produce a meaningful error message indicating a syntax error in the connection string.

Changed behavior