Exasol JDBC Driver should throw error on invalid parameter in connection string and connection string properties
Details
| Detail name | Value |
|---|---|
| Changelog Number | 21749 |
| Type | Improvement |
| Status | Resolved |
| Fix Versions | JDBC 24.2.0 |
| Resolution Date | 2024-11-11 |
Background
In CHANGELOG: JDBC: Raise Exception in case of invalid connection string argument Exasol JDBC driver was improved to validate parameters passed via connection string.
Improvement
The Exasol JDBC Driver has been updated to detect invalid parameters in both the connection string and properties. This improves the reliability and predictability of the driver by providing better feedback and avoiding unexpected behavior and difficult-to-debug connection issues. The changes include improved error handling, fixing an issue where unknown parameters in connection string properties were not detected, and improved parameter validation for improved security and stability. It is recommended that all users upgrade to the latest version of the Exasol JDBC driver to take advantage of these improvements.
Unknown Parameter in Connection String
Exception: [ERROR] Connection String does not support ([ARGUMENT]) argument.
Unknown Parameter in Connection Properties
Exception: [ERROR] Connection Properties does not support ([ARGUMENT]) argument.
If a frontend / client application wants to add an unknown parameter, then driver will throw the above error. If it’s strictly necessary for the frontend / client application to pass a parameter that is not known to Exasol JDBC driver, the unknown parameter can be added in ignoreparams parameter.
See CHANGELOG: JDBC Improved Handling of Invalid Connection String Parameters for details about the ignoreparams parameter feature and JDBC Driver for the list of available parameters and their usage notes.
Changed behavior
Exasol JDBC Driver now throws an error on invalid parameters in both connection string and properties.
This improves the driver's reliability and predictability by providing better feedback and avoiding unexpected behavior and difficult-to-debug connection issues.
