All pages
Powered by GitBook
1 of 1

Loading...

Connector/ODBC 2.0.16 Changelog

The most recent Stable (GA) release of MariaDB Connector/ODBC is:MariaDB Connector/ODBC 3.2.5

DownloadRelease NotesChangelogAbout MariaDB Connector/ODBC

Release date: 8 Feb 2018

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 #d93b0b8 2018-02-04 23:01:24 +0100

    • [] The fix and the test-case. Fetch would fail, if unbound column contained NULL, and for that column some arbitrary descriptor field was set by application(but not value/len/ind buffer ptrs). The bug affected ADO, as that is something it can do with CursorLocation adUseClient in some cases

  • 2018-02-01 10:20:13 +0100

    • For the info type SQL_SCHEMA_TERM/SQL_OWNER_TERM the connector returned wrong length. Or more exactly - did not write anything into application's length buffer. The fix and the test-case. Possibly fixes .

  • 2018-01-28 23:21:04 +0100

    • [] The fix and the test-case. The connector ordered SQLStatistics results using wrong columns. That could cause MS Access to pick wrong column as a unique index. And that, in its turn, could cause mangled data shown for the linked table. Fix of the test-case in catalog2 that failed against 10.3 due to new privilege. Added test of SQL_GROUP_BY info to test-case. It had similar problem(and tested in similar way) Fixed build in VS2017

  • 2018-01-17 14:48:56 +0100

    • Small fix of the testcase for SQLProcedureColumns - reference values for RADIX field were wrong for 2 parameters. Has to be 10(or theoretically 2) for numeric types

  • 2018-01-26 16:21:06 +0100

    • Fix bug in ABI analogous to []

  • 2018-01-21 23:38:16 +0100

    • [] The fix and the test-case. While linking a table, MS Access threw the error when it received unexpected length for SQLSMALLINT and SQLINTEGER columns from SQLColumns resultset. New graphic images for the installer on Windows.

  • 2018-01-13 18:02:15 +0100

    • Temporary turned off tests atainst MaxScale in Travis

  • 2018-01-12 17:50:40 -0500

    • Addition to the fix of and the testcase for that problem - for SQL_CATALOG_LOCATION info type the connector incorrectly wrote to the buffer SQLUINTEGER, while it has to be SQLUSMALLINT

  • 2018-01-10 20:54:38 +0100

    • [] The fix and testcases. Some of internal structures weren't reallocated in accordance with the next resultset fields count. Beyond the case described in the report, they cover the case of statements batch. It had similar and own problems. Removed unused property from the statement structure.

  • 2017-12-27 21:46:48 +0100

    • [] The fix and the test-case. LibreOffice sets SQL_ATTR_USE_BOOKMARKS attribute, but does not actually use bookmarks. The connector was not ready for that, and would throw wrongly error, and then crash. Fixed a number of compilation warnings.

  • 2017-12-13 12:07:27 +0000

    • Don't space pad parameters with non-zero scale

  • 2017-12-19 19:16:55 +0100

    • Fix of waring from recent pull request

  • 2017-12-13 10:49:18 +0000

    • Return correct scale for SQL_C_NUMERIC

  • 2017-12-06 23:56:35 +0100

    • Addition for the fix of - optimization only used for FORWARD_ONLY cursors in this branch. Correction of merge error - tests detected Travis in wrong way

  • 2017-11-17 18:40:02 +0100

    • Fixed connection procedure call in couple of tests, since 1 parameter type was changed in previous commit, and these references were overlooked. Skipping connstring in Travis. Fixed SQL_API SQLTablePrivilegesW - it would always return empty resultset if CatalogName is NULL. That was not intended, and its ANSI counterpart doesn't behave like that.

  • 2017-12-03 16:25:51 +0100

    • Adding server to Travis tests. Skipping one tests with 5.5 servers(and MySQL <5.7), since it doesn't make sense there.

  • 2017-11-27 22:32:02 +0100

    • Fixing remaining issues in Travis Made (most of) tests framework global variables static, as one of them clashed with variable in connector's env, and that caused problems in some cases. Also fixed few tests in connstring, that expected test connection to use password. Skipped one of tests there(in connstring) on travis.

  • 2017-11-23 01:30:48 +0100

    • [] Fix of the performance issue. We did redundant calls of mysql_stmt_data_seek. They are needed for different type of cursors, positioned operation, array fetch etc. But in forward_only cursor it only significantly slows down execution.

  • 2017-11-14 13:02:13 +0200

    • Fix of testcases failing in Travis. Mostly that is adding cursor closing, as older UnixODBC versions require it even there it is not really required. One test in catalog2(bug50195) was expecting, that db server is on the same host with tests(that is not the case in Travis). Added Travis detection in the tests framework.

  • 2017-11-09 13:48:59 +0200

    • Changed DSN parsing/saving/reading tests(connstring.c) in order they do not fail with unixODBC. UnixODBC has buggy ini cache(which seemingly will be fixed in 2.3.5): if dsn is changed, and then read again, application will get old cached value. That doesn't occur if unixODBC is built with --enable-inicaching=no Thus tests have been changed to create and use individual DSN's, rather then one common for all tests DSN.

  • 2017-10-19 15:51:54 +0200

    • Initial Travis setup

  • 2017-10-09 19:58:56 +0300

    • Fixed one small memory leak - SQLSetCursorNameW leaked recoded (into ANSI or utf8 encoding) name. Added freeing of allocated memory in a couple of tests, so they don't create noise in valgrind. Enabled test of "where current of" - it was skipped with misleading "unsupported" message, and it doesn't fail.

  • 2017-10-09 16:54:20 +0300

    • Enabled test of updateable cursor (SQLSetPos with SQL_UPDATE), it was skipped with misleading "unsupported" message, and it doesn't fail.

  • 2017-10-06 21:17:19 +0200

    • Fix of the memory leak. It could occur if prepare, or direct execution in case of 10.2, failed, and Stmt handler is reused. Also removed unused field from Stmt struct and its references (was only freed in few places).

  • 2017-10-04 23:48:52 +0200

    • [] The fix and the testcase. Fix and the testcase. Wrong rc and sqlstate for numeric overflow (but not for fractional truncation). Now the connector returns 22003 and SQL_ERROR. Also changed int SQLFetch couple of switches to switch on Concise_Type, and not Type, that was seemingly wrong. Changed logo in the READMC.md

  • 2017-08-28 12:27:17 +0200

    • [] The Fix and the testcase of the crash in case of columns unbinding after stmt execution and before fetching data. The reason was freeing of 2 internal arrays that are allocated during execution and reset at each fetch. SQLFreeStmt(SQL_UNBIND) just shouldn't free them.

  • 2017-07-31 02:30:34 +0200

    • [] Starting from v. 10.2.7, server encloses COLUMN_DEFAULT in the INFORMATION_SCHEMA.COLUMNS table, in single quotes for literal strings. Connector now considers the server version, when constructing the query for SQLColumns.

  • 2017-06-22 16:56:39 +0200

    • Merge pull request #15 from jacquesg/include-guard

  • 2017-06-22 14:12:19 +0200

    • correct include guard

ODBC-134
Revision #d506530
ODBC-109
Revision #e7e12ae
ODBC-119
ODBC-123
Revision #ce44b4d
Revision #8f34a4e
ODBC-123
Revision #dbc6409
ODBC-131
Revision #e84bdcc
Revision #4f8bdb9
ODBC-123
Revision #a22bf42
ODBC-126
Revision #b085030
ODBC-123
Revision #99ccc9e
Revision #528df54
Revision #4ab2f82
Revision #7c445fb
ODBC-120
Revision #c077544
Revision #d9c0ff4
MariaDB 5.5
Revision #27daadc
Revision #0f69c54
ODBC-120
Revision #553bc88
Revision #714acf9
Revision #514a892
Revision #20c43cc
Revision #e475a3d
Revision #9ea9f21
Revision #bb86bf1
ODBC-115
Revision #33116e2
ODBC-110
Revision #064a189
ODBC-105
Revision #ab661fb
Revision #cd24ea5

This page is: Copyright © 2025 MariaDB. All rights reserved.