Releases: exasol/exasol-driver-go
0.3.2: Fix `ToDSN()` to add the schema
Exasol Go SQL Driver 0.3.2, released 2022-04-21
Code name: Fix ToDSN()
to add the schema
Summary
This release fixes a bug in the ToDSN()
that caused the schema to be missing in the generated DSN.
Bugfixes
- #56: Added the schema to
ToDSN()
.
Version 0.3.1: Security updates
Exasol Go SQL Driver 0.3.1, released 2022-03-30
Code name: Security updates
Summary
Update dependencies to fix security issues:
Dependency Updates
Direct Dependencies
- Updated
github.com/exasol/error-reporting-go v0.1.0
tov1.1.1
- Updated
github.com/testcontainers/testcontainers-go v0.12.0
tov0.12.1
Indirect Dependencies
- Added
github.com/containerd/containerd v1.6.2
- Added
github.com/docker/distribution v2.8.1+incompatible
- Added
github.com/opencontainers/runc v1.1.1
- Added
github.com/docker/docker v20.10.14+incompatible
Version 0.3.0: CSV import
Exasol Go SQL Driver 0.3.0, released 2022-02-16
Summary
This release allows the import of multiple local CSV files via SQL and makes the ParseDsn()
function public.
Features
Dependency Updates
- Updated
github.com/gorilla/websocket v1.4.2
tov1.5.0
- Updated
github.com/testcontainers/testcontainers-go v0.11.1
tov0.12.0
Verify TLS Certificate Fingerprints
Exasol Go SQL Driver 0.2.0, released 2021-10-20
Code name: Verify TLS Certificate Fingerprints
Summary
This release contains a breaking change: We renamed the URL property usetls
to validateservercertificate
and method DSNConfig.UseTLS()
to DSNConfig.ValidateServerCertificate()
. The new names align with the JDBC driver's property validateservercertificate
.
To migrate to the new version, you only need to rename all occurances of usetls
to validateservercertificate
and all occurances of UseTLS
to ValidateServerCertificate
. The semantic has not changed, so you don't need to modify the values.
We also added support for TLS certificate fingerprints, similar to the JDBC driver. This is especially useful when your Exasol database uses a self-signed certificate or the certificate contains the wrong hostname. See the documentation for details.
The new release also uses error-reporting-go to provide error messages with a unique ID, e.g. E-EGOD-4
. This will allow us to generate a catalog of all error messages in a central location.
Features
- #37: Verify TLS certificate fingerprints
- #42: Use error-reporting-go to generate Exasol error messages
Bugfixes
Refactoring
- #36: Renamed URL property
usetls
tovalidateservercertificate
.
Fixed connection to Exasol 7.1.0 and later
Fixed connection to Exasol 7.1.0 and later
Fixed fetching data from a result set
Initial implementation of Exasol Go SQL Driver
Summary
This is an initial implementation of the Exasol Go SQL Driver for connection to the Exasol database.
This library implements the standard Golang SQL driver interface for easy use.
How to use it In a nutshell:
package main
import (
"database/sql"
"github.com/exasol/exasol-driver-go"
)
func main() {
database, err := sql.Open("exasol", exasol.NewConfig("<username>", "<password>").Port(<port>).Host("<host>").String())
...
}
For additional information please refer to the documentation: https://github.com/exasol/exasol-driver-go
Features
- #3: Added error logging.
- #5: Added first integration test.
- #6: Added DSN builder.
- #14: Implemented host with multiple values.