JDBC Connection String Parameters Are Now Case Insensitive
Details
| Detail name | Value |
|---|---|
| Changelog Number | 26124 |
| Type | Improvement |
| Status | Resolved |
| Fix Versions | JDBC 25.2.5 |
| Resolution Date | 2025-08-19 |
Background
In previous versions, JDBC connection string parameters were case sensitive, requiring developers to use the exact casing as expected by the system. This behavior often led to errors when parameter names were provided in an incorrect case, causing additional debugging and configuration challenges.
With this update, JDBC connection string parameters are now treated as case insensitive. Users can specify parameters in any combination of uppercase or lowercase letters, making it easier to configure connections without worrying about strict casing rules. This enhancement simplifies usage, aligns with widely accepted practices, and improves overall flexibility and user experience.
Improvement
- Parameters in the JDBC connection string can now be specified in any case (e.g., uppercase, lowercase, or mixed case).
- Resolved issues caused by case mismatches that previously resulted in runtime errors.
Example Before Update:
Connection String: jdbc:exa:localhost:8795/nocertcheck;ENCRYPTION=0
Exception:
[ERROR] Connection String does not support (ENCRYPTION) argument.
Example After Update:
Connection String: jdbc:exa:localhost:8795/nocertcheck;ENCRYPTION=0
Result: The parameter ENCRYPTION will now be properly recognized whether specified as ENCRYPTION, encryption, or any other case variation.
Impact:
- Users no longer need to conform to strict case rules when declaring JDBC connection string parameters.
- Existing configurations remain unaffected—all previously working case-sensitive strings will continue to function.
- Developers can use both uppercase and lowercase parameter names interchangeably without encountering errors.
