7 MYSQL

============================================================================== Simba MySQL ODBC Driver Release Notes ==============================================================================

The release notes provide details of enhancements, features, known issues, and workflow changes in Simba MySQL ODBC Driver 1.0.19, as well as the version history.

1.0.19 =======================================================================

Released 2020-12-31

Enhancements & New Features

  • [MYSQLO-621][MYSQLO-623] Updated precision for SQL data types

    The precision for the following SQL data types has been updated:

    • SQL_TIME has a precision of 9 for fractional seconds.
    • SQL_FLOAT and SQL_DOUBLE conversions to SQL_C_CHAR and SQL_C_WCHAR have a maximum precision of 15.

Resolved Issues The following issue has been resolved in Simba MySQL ODBC Driver 1.0.19.

  • [MYSQLO-619] MySQL queries take twice as long as expected to execute.

Known Issues The following are known issues that you may encounter due to limitations in the data source, the driver, or an application.

  • [MYSQLO-540] If the input value of the ColumnSize parameter in a SQLBindParameter() function call is greater than 4294967295, the value is reduced to 4294967295.

  • Cursors are non-scrollable.

    The driver only supports forward-only cursors; it does not allow cursors to move backward through query results. This driver behaviour is consistent with the behaviour that is officially defined for MySQL cursors, which are non-scrollable.

  • Local Socket/Pipe connections are not supported.

    The driver does not support named pipe or socket file connections. You must connect to the server using a TCP/IP connection.

  • Query bookmarks are not supported.

    The driver cannot create query bookmarks or retrieve information from existing bookmarks.

  • Positioned statements are not supported.

    The driver cannot execute statements on the rows from a result set.

  • External authentication plugins are not supported.

    The driver does not support the following authentication plugins:

    • PAM
    • Cleartext client-side
    • Socket peer-credential

    Instead, use the caching_sha2_password, native, SHA-265, or Windows native authentication plugins.

  • Driver only supports the utf8mb4 character set.

    Currently, the driver cannot use different character sets when working with data.

  • [MYSQLO-611] When using RHEL 8 with dynamic linking, and the cryptographic policy is set to default or higher, the driver returns an error for certificates with a key length of less than 2048.

    As a workaround, increase the key length or set the cryptographic policy to legacy.

Workflow Changes =============================================================

The following changes may disrupt established workflows for the driver.

1.0.18 ———————————————————————–

  • [MYSQLO-515][MYSQLO-517] Removing support for earlier versions of operating systems

    Beginning with this release, the driver no longer supports the following operating systems:

    • Windows 7
    • Windows Server 2008
    • Windows Server 2008 R2
    • macOS 10.12 “Sierra”
    • CentOS 6
    • Red Hat Enterprise Linux (RHEL) 6
    • Debian 8

    For information about supported operating systems, see the Installation and Configuration Guide.

1.0.13 ———————————————————————–

  • [MYSQLO-469] Ubuntu 14.04 and SLES 11 no longer supported

    Beginning with this release, the driver does not support Ubuntu 14.04 and SUSE Linux Enterprise Server (SLES) 11.

1.0.7 ————————————————————————

  • Minimum TLS Version

    Beginning with this release, the driver requires a minimum version of TLS for encrypting the data store connection. By default, the driver requires TLS version 1.2. This requirement may cause existing DSNs and connection strings to stop working, if they are used to connect to data stores that use a TLS version earlier than 1.2.

    To resolve this, in your DSN or connection string, set the Minimum TLS option (the Min_TLS property) to the appropriate version of TLS for your server. For more information, see the Installation and Configuration Guide.

Version History ==============================================================

1.0.18 ———————————————————————–

Released 2020-09-30

Enhancements & New Features

  • [MYSQLO-605] Updated logging configurations

    You can now configure logging for the current connection by setting the logging configuration properties in the DSN or in a connection string. For more information, see the Installation and Configuration Guide.

  • [MYSQLO-610] Updated OpenSSL version

    The driver now uses OpenSSL version 1.1.1g. Previously, the driver used OpenSSL version 1.1.1d.

1.0.17 ———————————————————————–

Released 2020-08-28

Resolved Issues The following issue has been resolved in Simba MySQL ODBC Driver 1.0.17.

  • [MYSQLO-585] In some cases, MySQL string types with binary collation map to SQL_LONGVARBINARY instead of SQL_WLONGVARCHAR.

1.0.16 ———————————————————————–

Released 2020-06-30

Enhancements & New Features

  • [MYSQLO-554] Support for ANSI quotation marks

    The driver can now treat a quotation mark (") as an identifier quote character, rather than a string quote character. To enable this, select the Enable ANSI Quotes check box (set the ANSI_QUOTES connection property to True). For more information, see the Installation and Configuration Guide.

  • [MYSQLO-573] Instructions for OEM installation

    The driver package now includes instructions for OEM driver installation. For more information, see the Simba OEM ODBC Drivers Installation Instructions.

Resolved Issues The following issues have been resolved in Simba MySQL ODBC Driver 1.0.16.

  • [MYSQLO-542] The SQLEndTran function does not send a Commit request.

  • [MYSQLO-557] In some cases, when you delete a table in which a transaction was executed, the driver becomes nonresponsive.

1.0.15 ———————————————————————–

Released 2020-04-24

Enhancements & New Features

  • [MYSQLO-530] Support for MySQL spatial data types

    The driver now supports MySQL spatial data types. These data types are mapped to SQL_LONGVARBINARY. For more information, see the Installation and Configuration Guide, or see “Spatial Data Types” in the MySQL documentation: https://dev.mysql.com/doc/refman/5.7/en/spatial-type-overview.html

  • [MYSQLO-534][MYSQLO-547] Support for unsigned integers

    The driver now supports unsigned integers. For more information, see the Installation and Configuration Guide.

Resolved Issues The following issues have been resolved in Simba MySQL ODBC Driver 1.0.15.

  • [MYSQLO-528] When you bind a large number of parameters, the driver returns an “Incorrect arguments to mysqld_stmt_execute” or “Malformed packet” error.

  • [MYSQLO-533] In some cases, when you insert parameterized binary data, the driver returns an error.

  • [MYSQLO-534] When the driver converts large unsigned integers from SQL_C_SBIGINT C type to SQL_INTEGER SQL type, it returns an error.

  • [MYSQLO-541] SQLParamData returns “No data can be obtained from an input parameter whose value has already been pushed down” when the input parameter has been pushed down.

  • [MYSQLO-547] When the driver converts unsigned integer values that are in the valid range of TINYINT UNSIGNED, SMALLINT UNSIGNED, MEDIUMINT UNSIGNED, or BIGINT UNSIGNED, it returns a “Numeric Value out of range” error.

1.0.14 ———————————————————————–

Released 2020-04-03

Enhancements & New Features

  • [MYSQLO-518] Support for additional systems

    The driver now supports the following operating systems:

    • macOS 10.15 “Catalina”
    • Red Hat Enterprise Linux 8
    • CentOS 8

  • [MYSQLO-511] Upgrade Expat to 2.2.9

    The driver now uses Expat 2.2.9 for XML parsing. Previously, the driver used Expat 2.2.7.

Resolved Issues The following issue has been resolved in Simba MySQL ODBC Driver 1.0.14.

  • [MYSQLO-503] The driver terminates unexpectedly when both of the following occur:
    • Multiple database drivers are loaded to the same process.
    • One driver unloads and calls ICU’s u_cleanup() function, while another driver continues to run and tries to access the memory space that has been cleaned up.

1.0.13 ———————————————————————–

Released 2019-11-15

Enhancements & New Features

  • [MYSQLO-494] Updated system requirements

    The system requirements for the driver has been updated. For more information, see the Installation and Configuration Guide.

  • [MYSQLO-442] Updated support for Debian installation

    The Linux driver now includes installation packages specific to Debian systems. For more information, see the Installation and Configuration Guide.

  • [MYSQLO-475] Updated driver version information in Linux binary

    You can now check the Linux driver’s version from the driver binary file. To do this, open the .so file in a text editor, and search for the text “\(driver_version_sb\):”. The driver’s version number is listed after this text.

  • [MYSQLO-450] Upgrade to OpenSSL 1.1.1d

    The driver now uses OpenSSL 1.1.1d for encryption of data. Previously, the driver used OpenSSL 1.1.0j.

  • [MYSQLO-477] Updated third-party library linking for Linux

    In the Linux driver, minor internal improvements have been implemented for the linking between the third-party libraries and the main driver library.

  • [MYSQL0-471] Internal driver improvements

    The driver has been updated with minor internal improvements.

Resolved Issues The following issue has been resolved in Simba MySQL ODBC Driver 1.0.13.

  • [MYSQLO-487] Queries that contain binding parameters do not pass the data dynamically to the database.

1.0.12 ———————————————————————–

Released 2019-04-26

Resolved Issues The following issue has been resolved in Simba MySQL ODBC Driver 1.0.12.

  • [MYSQLO-458] When a column of type VARCHAR is defined using a COLLATE function, the column is mapped to byte[].

1.0.11 ———————————————————————–

Released 2019-03-29

Enhancements & New Features

  • [MYSQLO-444][MYSQLO-445] Support for MySQL Server 8.0

    The driver now supports MySQL Server 5.6, 5.7, and 8.0.

  • [MYSQLO-440] Custom maximum name lengths

    You can now customize the maximum length of the names of catalogs, schemas, tables, and columns. You set these lengths through the connection properties MaxCatalogNameLen, MaxSchemaNameLen, MaxTableNameLen, and MaxColumnNameLen. For more information, see the Installation and Configuration Guide.

  • [MYSQLO-433] More informative error messages for port settings

    The driver now provides more detailed error messages when an invalid value is specified for the Port connection property.

  • [MYSQLO-451] Updated default authentication method

    The driver now uses the caching_sha2_password plugin as the default authentication method.

  • [MYSQLO-431] Dynamically linked third-party libraries

    The Linux driver has been updated to use dynamically linked libraries for ICU and OpenSSL. The installation directory now includes a “ThirdParty” directory which contains all required runtime libraries for the driver.

  • [MYSQLO-447] Updated OpenSSL version

    The driver now uses OpenSSL version 1.1.0j. Previously, the driver used OpenSSL version 1.1.0i.

1.0.10 ———————————————————————–

Released 2019-02-08

Enhancements & New Features

  • [MYSQLO-441] Updated ICU version

    The driver now uses ICU version 58.2.x.

Resolved Issues The following issue has been resolved in Simba MySQL ODBC Driver 1.0.10.

  • [MYSQLO-432] When the driver is installed on a machine that uses Turkish locale settings, if you try to connect using a connection string where one or more of the property names contains a lower-case “i” character, the driver fails to parse the string and does not connect to the server.

1.0.9 ————————————————————————

Released 2018-11-15

Enhancements & New Features

  • [MYSQLO-421][MYSQLO-423] Upgraded third-party libraries

    The driver now uses zlib version 1.2.11, and OpenSSL 1.1.0i.

  • [MYSQLO-414] Standardized log file names

    When logging is enabled, the driver now produces the following log files:

    • A simbamysqlodbcdriver.log file that logs driver activity that is not specific to a connection.

    • A simbamysqlodbcdriver_connection_[Number].log for each connection made to the database, where [Number] is a number that identifies each log file. This file logs driver activity that is specific to the connection.

==============================================================================