Documentation Home
MySQL Connector/ODBC Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 399.9Kb
PDF (A4) - 399.5Kb


MySQL Connector/ODBC Release Notes  /  Changes in MySQL Connector/ODBC Version 8.x  /  Changes in MySQL Connector/ODBC 8.0.19 (2020-01-13, General Availability)

Changes in MySQL Connector/ODBC 8.0.19 (2020-01-13, General Availability)

Functionality Added or Changed

  • Added DNS SRV support.

    To automatically resolve any SRV record available in a target DNS server or service discovery endpoint, specify ENABLE_DNS_SRV=1 in the DSN; the host is passed for SRV lookup without a port and with a full lookup name. For example: DRIVER={MySQL ODBC 8.0 Driver};SERVER=_mysql._tcp.foo.abc.com;ENABLE_DNS_SRV=1;USER=user;PWD=passwd; (WL #13403)

  • Confirmed support for compiling with VS2019, and for supporting the Visual C++ 2019 redistributable. (WL #13564)

  • When creating a new connection using the classic MySQL protocol, multiple hosts can be tried until a successful connection is established. A list of hosts can be given in a connection string, along with passing MULTI_HOST=1 to to enable this functionality. The connection string looks similar to SERVER=address1[:port1],address2[:port2]....;MULTI_HOST=1;.

    Other notes: the default port is used if port is not specified, the connector randomly picks hosts, and if a host fails then a new host is chosen. An error is returned if SERVER contains multiple hosts when MULTI_HOST is not enabled. (WL #13323)

Bugs Fixed

  • With prepared SELECT statements the fixed-length numeric types such as INT were set to 0 instead of their stored value, if a textual field was also part of the SELECT statement. (Bug #30428851, Bug #97191)

  • Connector/ODBC failed to compile when dynamically linking to the MySQL client library (MYSQLCLIENT_STATIC_LINKING=0); due to a mismatch between an internal copy of the library headers and the version of code implementing the library internals. (Bug #30292290, Bug #96835)

  • Improved handling for stored procedures and the INOUT parameter.

    For example, if a stored procedure had one or more parameters then an incomplete result set could be returned. (Bug #29467224, Bug #94623)