MariaDB Connector/ODBC 3.0.9 Changelog

Download Release Notes Changelog About MariaDB Connector/ODBC

Release date: 3 May 2019

For the highlights of this release, see the release notes.

The revision number links will take you to the revision's page on GitHub. On GitHub you can view more details of the revision and view diffs of the code modified in that revision.

• Revision #832360f 2019-05-02 20:21:24 +0200
  • ODBC-211 The fix and the testcase
    • Also fixed precision, octet length, and display size calculation in case of unsigned decimal field and/or 0 scale.
• Revision #38e4205 2019-04-26 00:12:16 +0200
  • ODBC-225 The fix and updated testcases
    • The driver treated NULL values as empty strings when checked if the SQLTables call is special case for the databases list return.
    • Also contains fixes for ODBC-245 and ODBC-246
• Revision #1e633f8 2019-04-09 00:47:36 +0200
  • ODBC-238 Added FORCETLS connection string option
    • This is for implementation of the C/C MYSQL_OPT_SSL_ENFORCE option, which enables forcing TLS use
• Revision #9d1d94b 2019-04-08 15:30:40 +0200
  • ODBC-239 Changed mysql_options calls as it's deprecated
• Revision #3b39fe0 2019-04-04 19:28:45 +0200
  • Version bump -> 3.0.9
• Revision #031e0ac 2019-03-23 16:30:52 +0100
  • Making sure SSL options are not empty strings and not white spaces only. That shouldn't normally happen, as the connector trims dsn field values, and does not store empty strings. But better to be safe.
• Revision #fb0ac79 2019-03-21 23:18:47 +0100
  • ODBC-232 The fix and the testcase
    • This bug boils down to a crash in SQLGetData if an application unbinds result buffers after execution, i.e. calls SQLFreeStmt(SQL_UNBIND). That happened because SQL_UNBIND freed columns metadata along with freeing bind buffers.
• Revision #172c399 2019-03-21 15:36:41 +0100
  • ODBC-228 Added connection string option TLSVERSION
    • This option can be used to enforce MARIADB_OPT_TLS_VERSION C/C option to limit allowed for the connection TLS versions.
    • The value can be either a bitmap, where bit 1 corresponds to TLSv1.1, bit 2 - TLSv1.2, and 4 - to TLSv1.3, or it can be set as combination of string names TLSv1.1, TLSv1.2 and TLSv1.3.
    • Checkbox group has been added to the Windows setup dialog. If no checkbox is checked there means all versions are allowed.
    • The testcase tests only correct connection string parsing/storing
    • The file win/ma_odbc_setup.h has been moved to 'dsn' directory, as there was already the file with the same name, that wasn't used. 'win' directory has been removed, since that was the only file there
• Revision #21864d5 2019-03-19 22:13:05 +0100
  • ODBC-229 Added option for reading section in my.cnf
    • Connection string option is USE_MYCNF. OPTIONS bit 65536 may also be used.
    • The checkbox for the option has been added to Windows setup dialog. Removed some garbage from rc file along the way. Test of the option has been added to connstring.
• Revision #1aad919 2019-03-18 14:57:46 +0100
  • ODBC-234 The fix only - not new tests needed
    • ODBC-233 will enable tests for this bug
• Revision #553c71f 2019-03-17 23:25:49 +0100
  • ODBC-231 The fix and the testcase.
    • The bug is actually in SSIS. It binds column size as signed int, but the value for LONGTEXT is max unsigned int. Connector was returning truncation error on the row fetch. And that is probably not quite right. The patch makes connector not to return truncation error in case if truncation is caused solely by sign-ness of the field/buffer.
• Revision #5165a90 2019-03-14 21:20:01 +0100
  • The fix of the build in travis with latest C/C release
• Revision #35f9e5d 2019-03-13 20:55:57 +0100
  • ODBC-219 The fix and the testcase.
    • This bug boils down to not reporting correct columns count in case of a query with multiple results(stored procedure or statements batch) if the result with affected rows count followed a resultset.
    • In case of stored procedure(like in the bug report) this is always the case, if SP returns a result set.
    • The bug occured becaule IRD was not reset in the SQLMoreResults in the described case.
    • Fixed mistake in previous commit(for ODBC-216) - lost statement handler reinitialization in one place.
• Revision #8d22a84 2019-02-28 23:41:21 +0100
  • ODBC-216 The fix and the testcase.
    • Connector returned wrong value for SQL_DESC_FIXED_PREC_SCALE. In the report it was going about bigint type, but in fact for many other types SQL_TRUE was returned, where it shouldn't be. Since definition of SQL_DESC_FIXED_PREC_SCALE is not clear, we checked what SQL Server driver returns for different types for reference. Only for (small)money types SQL_TRUE is returned. For types that has counterparts in MariaDB, SQL_FALSE is always returned. Thus, SQL_FALSE has been made a default value for all types for the SQL_DESC_FIXED_PREC_SCALE field.
• Revision #aaba291 2019-01-24 15:54:55 +0100
  • Fix of error made in tests framework by previous commit
• Revision #646803f 2019-01-23 21:28:59 +0100
  • ODBC-213 The fix and the testcase
    • SQL_DESC_PARAMETER_TYPE was returned in wrong type - integer instead of small integer. Also, application could get it not only from Ipd descriptor, but also from Ird.