MariaDB Connector/ODBC 2.0.16 Changelog

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
  • [ODBC-134] Fix and testcase. 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 in some cases with CursorLocation adUseClient
• Revision #d506530 2018-02-01 10:20:13 +0100
  • Fix and testcase of the bug, that was found during investigation on ODBC-109. It's not clear atm if the bug causes the reported error in the connector's work, since I can't reproduce the bug. But looks probable. 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
• Revision #d4d8c72 2018-01-29 14:06:30 +0100
  • Slightly changed the test failing on Travis - using KILL on travis instead of timeout emulation, mnd ade some better output.
• Revision #e7e12ae 2018-01-28 23:21:04 +0100
  • [ODBC-119] The fix and testcase. The connector ordered SQLStatistics results using worng 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 testcase in catalog2 that failed against 10.3 due to new privelege. Added test of SQL_GROUP_BY info to ODBC-123 testcase. It had similar problem(and tested in similar way) Fixed build in VS2017
• Revision #ce44b4d 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
• Revision #8f34a4e 2018-01-26 16:21:06 +0100
  • Fix bug in ABI analogous to [ODBC-123]
• Revision #dbc6409 2018-01-21 23:38:16 +0100
  • [ODBC-131] Fix and the testcase. While linking table in MS Access, it threw error when it received unexpected length for SQLSMALLINT and SQLINTEGER columns from SQLColumns resultset. New graphic images for the installer on Windows.
• Revision #e84bdcc 2018-01-13 18:02:15 +0100
  • Temporary turned off tests atainst MaxScale in Travis
• Revision #4f8bdb9 2018-01-12 17:50:40 -0500
  • Addition to the fix of ODBC-123 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
• Revision #a22bf42 2018-01-10 20:54:38 +0100
  • [ODBC-126] 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.
• Revision #b085030 2017-12-27 21:46:48 +0100
  • [ODBC-123] Fix and testcase. 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.
• Revision #99ccc9e 2017-12-13 12:07:27 +0000
  • Don't space pad parameters with non-zero scale
• Revision #528df54 2017-12-19 19:16:55 +0100
  • Fix of waring from recent pull request
• Revision #4ab2f82 2017-12-13 10:49:18 +0000
  • Return correct scale for SQL_C_NUMERIC
• Revision #16fd599 2017-12-07 14:35:42 +0100
  • Correction in the travis config to actually run tests against MaxScale
• Revision #7c445fb 2017-12-06 23:56:35 +0100
  • Addition for the fix of ODBC-2.0 - optimizaiton only used for FORWARD_ONLY cursors in this branch. Correction of merge error - tests detected Travis in wrong way
• Revision #c077544 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. Changed in travis' script ODBCINI and ODBCSYSINI initialization to use PWD(not sure why:)). Added env var export for tests to detect Travis. Skipping connstring in Travis. I'd say this is harmless - it is kinda a special testsuite, and also to check if that is simply a linking problem(libodbcinst.so is the suspect). Fixed SQL_API SQLTablePrivilegesW - it would always return empty resultset in CatalogName is NULL. That was not intended, and its ANSI counterpart doesn't behave like that. Need to file bug report about that. But I suspect other catalog functions have the same problem.
• Revision #d9c0ff4 2017-12-03 16:25:51 +0100
  • Adding MariaDB 5.5 server to Travis tests. Skipping one tests with 5.5 servers(and MySQL <5.7), since it doesn't make sense there.
• Revision #27daadc 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.
• Revision #0f69c54 2017-11-23 01:30:48 +0100
  • [ODBC-120] Fix of performance issue. We did redundant calls of mysql_stmt_data_seek. They are neede for different type of cursors, positioned operation, array fetch etc. But in general forward_only cursor it only significantly slows down execution.
• Revision #553bc88 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) changed more profoundly, as it implied, that db server is on the same host with tests. Added Travis detection in the tests framework.
• Revision #714acf9 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. I guess what some of tests are not failing is rather the result of that bug :) Probably it'd be better to simply skip failing tests if run with (old version of) unixODBC Also merged from 3.0 generation of ini files for testing with UnixODBC.
• Revision #514a892 2017-10-19 15:51:54 +0200
  • Initial travis setup
• Revision #20c43cc 2017-10-09 19:58:56 +0300
  • Fixed one small memory leak - in the call to SQLSetCursorNameW leaked name recoded(in utf8) Added free-ing of allocated memory in couple of tests, so they don't create noise in valgrind Un-skipped test of "where current of" - again, noticed it was skipped, and it doesn't fail if un-skipped
• Revision #e475a3d 2017-10-09 16:54:20 +0300
  • Un-skipped test of updatebale cursor(SQLSetPos with SQL_UPDATE), since I've noticed it's being skipped, and it doesn't fail
• Revision #9ea9f21 2017-10-06 21:17:19 +0200
  • Fix of the memory leak. It could occur if prepare failed, and Stmt handler reused. Alse removed unused field from Stmt struct and its references(was only freed in few places).
• Revision #bb86bf1 2017-10-04 23:48:52 +0200
  • [ODBC-115] The fix and the testcase. Wrong rc and sqlstate for numeric overflow(but not for fractional truncation). Now connector returns 22003 and SQL_ERROR Also changed in SQLFetch couple of switches to switch on Concise_Type, and not on Type, that was seemingly wrong. Changed logo in the READMC.md
• Revision #33116e2 2017-08-28 12:27:17 +0200
  • [0DBC-110] Fix and testcase of the crash in case of columns unbinding after stmt execution and before fetching data. The reason was free-ing of 2 internal arrays, that are allocated during execution, and reset at each fetch. SQLFreeStmt(SQL_UNBIND) just shouldn't free them.
• Revision #064a189 2017-07-31 02:30:34 +0200
  • [ODBC-105] Connector now constructs query for SQLColumns considering server version.
• Revision #69d2299 2017-10-04 23:48:52 +0200
  • [ODBC-115] Fix and the testcase. Wrong rc and sqlstate for numeric overflow(but not for fractional truncation). Now connectors 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
• Revision #b3d56eb 2017-07-31 02:30:34 +0200
  • [ODBC-105] Starting from 10.2.8 server encloses COLUMN_DEFAULT in single quotes. Connector now constructs query for SQLColumns considering server version. Couple small changes alongside. SQLColAttribute returns HY091 instead of HYC00 for unknown attributes. And firxed error in IndicatorPtr calculation, that could probably affect positioned/bulk operations involving DAE parameters.
• Revision #ab661fb 2017-06-22 16:56:39 +0200
  • Merge pull request #15 from jacquesg/include-guard
• Revision #cd24ea5 2017-06-22 14:12:19 +0200
  • correct include guard
• Revision #41de3ed 2017-05-24 02:15:05 +0200
  • Version bump -> 2.0.16