Drivers: Rename from EXASolution to Exasol
Details
| Detail name | Value |
|---|---|
| Changelog Number | 17593 |
| Type | New Feature |
| Status | Resolved |
| Fix Versions | ODBC 24.0.0, JDBC 24.0.0, ADO.NET 24.0.0 |
| Resolution Date | 2024-03-11 |
New Feature
All drivers are renamed from “EXASolution” to “Exasol”. The behavior of the drivers are not changed.
Details
ODBC
All strings in the driver and all strings the driver outputs that had “EXASolution” inside contain now “Exasol”. This affects also error messages, instead of the prefix “[EXASOL][EXASolution driver]” the error messages now will contain “[EXASOL][Exasol driver]”.
ODBC on Windows
The Windows installer will now Install the “Exasol Driver” and a virtual “EXASolution Driver” that points to the Libraries of “Exasol Driver”. You can convert easily an existing EXASolution ODBC data source to an Exasol ODBC data source by opening it in the Windows ODBC administrator and saving the shown configuration by clicking the “OK” button.
The “EXASolution Driver” is kept only for backward compatibility and is deprecated. Only “Exasol Driver” data sources can be created from now on.
JDBC, ADO.NET
All strings, including error messages, that come from the driver and contained “EXASolution” now return “Exasol” in it’s place. All connections using this drivers will work like before, there are no changes in connection string parameters or public class names.
Changed behavior
Drivers are renamed from "EXASolution" to "Exasol". Any error messages showing "EXASolution" now show "Exasol" instead.
