Changelog for Exasol Driver¶
For full details, see the upstream changelog .
v0.12.6 (2026-06-08)¶
Fixes:
If a nonexistent schema is specified in the connection URI, the driver will still connect instead of failing
?characters inside string literals, quoted identifiers, and comments are no longer treated as bind parameter placeholdersMulti-value
WHERE col IN (...)now properly returns all matching rowsApply the
query_timeoutconnection parameter to all statementsUpdate dependencies with security advisories (see the upstream changelogs for details)
v0.12.0 (2026-04-30)¶
New features:
Use the native TCP transport instead of WebSocket by default for improved performance
Improve result set parsing performance
Directly upload Parquet data when importing (instead of converting to CSV)
Issue
OPEN SCHEMAif a schema is present in the connection URI (exasol://u:p@localhost:8563/my_schema)
v0.9.0 (2026-04-16)¶
New features:
Add support for validating TLS certificate fingerprints
Add support for 1024-bit RSA public keys during login (used by some instances, e.g.
demodb.exasol.com)( Breaking change) Default to
tls=truein connections to match Exasol 7.1+
Fixes:
Update dependencies with security advisories (see the upstream changelog for details)
v0.7.0 (2026-03-20)¶
New features:
Add support for GetObjects
Add support for GetParameterSchema
Add support for GetTableSchema
Add support for transactions
Add support for getting the current catalog
Fixes:
Fix support for large result sets
v0.6.3 (2026-03-03)¶
Initial release supporting query execution