Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Changelogs for MariaDB Connector/ODBC 3.0
The most recent Stable (GA) release of MariaDB Connector/ODBC is:MariaDB Connector/ODBC 3.2.5
DownloadRelease NotesChangelogAbout 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
The fix and the testcase
Also fixed precision, octet length, and display size calculation in case of unsigned decimal field and/or 0 scale.
2019-04-26 00:12:16 +0200
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 and
2019-04-09 00:47:36 +0200
Added FORCETLS connection string option
This is for implementation of the C/C MYSQL_OPT_SSL_ENFORCE option, which enables forcing TLS use
2019-04-08 15:30:40 +0200
Changed mysql_options calls as it's deprecated
2019-04-04 19:28:45 +0200
Version bump -> 3.0.9
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.
2019-03-21 23:18:47 +0100
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.
2019-03-21 15:36:41 +0100
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.
2019-03-19 22:13:05 +0100
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.
2019-03-18 14:57:46 +0100
The fix only - not new tests needed
will enable tests for this bug
2019-03-17 23:25:49 +0100
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.
2019-03-14 21:20:01 +0100
The fix of the build in travis with latest C/C release
2019-03-13 20:55:57 +0100
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.
2019-02-28 23:41:21 +0100
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.
2019-01-24 15:54:55 +0100
Fix of error made in tests framework by previous commit
2019-01-23 21:28:59 +0100
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.
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
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.
The most recent Stable (GA) release of MariaDB Connector/ODBC is:MariaDB Connector/ODBC 3.2.5
DownloadRelease NotesChangelogAbout MariaDB Connector/ODBC
Release date: 4 Jan 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 #7b463c1 2018-12-20 16:42:02 -0700
Fix multi-statement param realloc. Example use case: Prepare the following SQL statement: "INSERT INTO tbl (a,b) VALUES (?,?); SELECT 1 FROM tbl WHERE c = ?" First execution of prepared statement will work, second execution will segfault or cause memory corruption.
2019-01-03 19:15:48 +0100
Merge branch 'master' into .0
2018-10-17 12:39:33 +0100
Add SQL_OUTER_JOINS support to SQLGetInfo This is an older attribute that is largely superseded by the newer SQL_OJ_CAPABILITIES attribute but some software checks it first and only uses SQL_OJ_CAPABILITIES to get more details if SQL_OUTER_JOINS says they are supported.
2019-01-02 13:31:26 +0100
Updating libmariadb to the 3.0.8 release tag
2018-12-10 18:16:41 +0100
The patch moves string to date/time types conversion from C/C on C/ODBC side to better meet ODBC requirements.
2018-12-02 22:31:37 +0100
The fix and the testcase. The problem occurred only with data fetched as SQL_C_WCHAR. That happened because for statement handles after 1st one, there wasn't STMT_ATTR_UPDATE_MAX_LENGTH attribute set, and getting data as a widestring depends on max_length.
2018-11-30 01:16:37 +0100
SQLGetData did not return empty wide string
2018-11-28 01:33:13 +0100
odbc*.ini files were generated in CMAKE_SOURCE_DIR, instead of CMAKE_BINARY_DIR. That probably is not right, and they have to be along with tests binaries
2018-11-16 12:06:49 +0100
Version bump -> 3.0.8 + new logo in README.md
The most recent Stable (GA) release of MariaDB Connector/ODBC is:MariaDB Connector/ODBC 3.2.5
DownloadRelease NotesChangelogAbout MariaDB Connector/ODBC
Release date: 12 Oct 2017
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 #743255a 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
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-10-03 23:44:16 +0200
Some optimizations for bulk operations - length arrays are not allocated and filled for fixed length types.
2017-09-30 01:53:34 +0200
and - We don't copy useful arrays data to smaller arrays if there are rows to skip (113), and we don't use PS bulk operations for statements other than INSERT and UPDATE(117). For the former we set a corresponding indicator value in one of the columns. For the latter we now store the query type in the Stmt structure.
2017-09-29 13:46:57 +0200
Testcase: server doesn't support bulk operations for DELETE.
2017-08-28 12:27:17 +0200
Fix and 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-08-24 22:54:07 +0200
Making possible to link C/C dynamically. Cmake option MARIADB_LINK_DYNAMIC tells cmake to look for and configure to link against dynamic library. Fixed all remaining uses of not exported C/C symbols.
The most recent Stable (GA) release of MariaDB Connector/ODBC is:MariaDB Connector/ODBC 3.2.5
DownloadRelease NotesChangelogAbout MariaDB Connector/ODBC
Release date: 2 Aug 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 #baf2287 2018-07-31 23:23:29 +0200
Fix of memory leaks in the driver. Query structure delete routine was called in the wrong place for SQL_DROP, and thus wasn't invoked for single statement queries. Other leak would only occur in case of multistatement query preparing, and batches were not allowed for the connection. One more leak would occur if a batch of statements was optimized to be executed via text protocol. Also the fix of the memory leak in tests. Not really a problem, but created noise in valgrind output.
2018-07-31 13:39:02 +0200
Update of libmariabd module to v3.0.6
2018-07-27 17:35:33 +0200
The fix and the testcase. In case if the query is a multistatement, connector splitted it into individual statements, prepare one by one, and then execute one by one. In case if one of statements depends on execution of one of previous statements, application can get error(think of tmp table creation with select from it) or incorrect results. We can't do anything in case of SQLPrepare + SQLExecute. The patch fixes that for SQLExecDirect. Now connector prepares and immediately executes each statement in the batch.
2018-07-24 18:22:34 +0200
Wrong display size for decimal fields.
2018-07-23 15:17:00 +0200
Not including libmariadb into source package
2018-07-19 12:49:41 +0200
FileDSN creation - fix and testcase
2018-07-17 14:31:11 +0200
The fix and the testcase. Connector does some query parsing, in particular to know the type of the query. Mostly it is interested if query returns result. It didn't evaluate WITH correctly
2018-07-13 01:02:18 +0200
The fix and the testcase. Those aggregate functions, that caused error, returned LONGLONG value, and Access was getting it as SQL_C_LONG. The problem was that connector returned length of the data as 8(field's size), and not 4(requested C-type size), as specs prescribe.
2018-07-11 17:05:28 +0200
The fix and the testcase. Connector did not return length of string returned for SQL_IDENTIFIER_QUOTE_CHAR info type.
2018-07-10 12:50:27 +0200
Changed version to 3.0 in README files.
2018-07-09 12:47:04 +0200
The fix and the testcase. Display and column length did notinclude fractional part for (date) time types. Also octet length for those types was length of they string representation, while specs say it should be size of corresponding ODBC data structs.
2018-07-04 18:06:26 +0200
Fix of build with dynamic C/C linking
2018-07-03 01:05:41 +0200
Scale(DecimalDigits) IRD field wasn't set for (date) time/timestamp fields with second fractional part. Thus SQLDescribeCol retulrned 0 in DegitalDigitsPtr
2018-07-02 01:19:59 +0200
The fix and the testcase. Date(time) types had numerous issues with bulk operations. We provided array of buffers, and C/C expects array of pointers to buffers.
2018-06-27 00:51:56 +0200
The fix and the testcase. For fixed length types SQL_DESC_OCTET_LENGTH initialized by type length, rather than by BufferLength parameter value.
2018-06-25 14:11:34 +0200
The fix and extended old testcase. DESC statement caused error with the connector.
2018-06-18 14:36:35 +0200
the testcase and some amendments to the fix. Used OctetLengthPtr, since IndicatorPtr may be different from length ptr Version bump -> 3.0.6
2018-06-14 21:33:01 -0400
The field length is not set for DATE, TIME, or DATETIME values assigned during SQLFetch calls. Without the length set, Crystal Reports interprets all DATE, TIME, and DATETIME values as NULL. Setting *ArdRecord->IndicatorPtr to the size of the appropriate data structure in MADB_CopyMadbTimestamp.
The most recent (GA) release of MariaDB Connector/ODBC is:
Release date: 12 Jun 2018
For the highlights of this release, see the .
The revision number links will take you to the revision's page on GitHub. On you can view more details of the revision and view diffs of the code modified in that revision.
2018-06-07 00:08:08 +0200
Windows build fix
Revision #a6621de 2018-05-31 00:01:05 +0200
Version bump -> 3.0.5
Revision #62545da 2018-05-30 19:46:00 +0200
[ODBC-146] The fix and the testscase. Wrong decimal value (0) when after longtext field in select clause (using ADO, client side cursor)
Revision #8a15bdc 2018-05-30 00:26:03 +0200
Fixed dynamic linking against C/C
Revision #cfb393b 2018-05-28 16:26:26 +0200
[test] removing plugins from server test build. server test build can be build with plugins according to build options. This patch permit will not install those plugins (particulary mariadb-plugin-cracklib-password-check)
Revision #ea7a519 2018-05-28 17:41:20 +0300
Added version-script for non-windows platform
Revision #e674bd6 2018-05-22 14:46:39 +0200
Small test enhancement to check if correct length
Revision #0719af3 2018-05-04 11:39:45 +0200
[TODO-1299] testing connector against last server build. Those tests permit to check early regression and might failed, so tagged as "Allowed Failures" on travis
Revision #7da0dbb 2018-04-09 17:52:03 +0900
Fetching Multiple Result Set Crash - completion of ODBC-126 fix
Revision #860c985 2018-05-15 00:50:27 +0200
[ODBC-141] The fix and the testcase.
Revision #ad6dbb5 2018-05-03 20:05:35 +0200
[ODBC-143] Wrong SQL_IDENTIFIER_QUOTE_CHAR info in case of ANSI_QUOTES
Revision #2e46189 2018-04-04 13:14:12 +0200
Travis change for C/C as a subproject Subproject update to latest commit Fix of CTest configuration with new executable names
Revision #c0070c3 2017-01-18 08:54:34 -0800
Windows build fixes
Revision #cc0f481 2017-01-18 16:11:56 +0100
Add Connector/C plugins into package
Revision #1560f9d 2017-01-18 08:52:30 +0100
use tag v3.0.1-beta for Connector/C
Revision #4860a43 2017-01-18 08:30:35 +0100
Added helper script for retrieving connector/c sources
Revision #76a37b7 2017-01-18 08:11:10 +0100
Build Connector/ODBC with git subproject Connector/C. Connector/C will be installed in libmariadb
Revision #025978c 2018-03-27 16:54:19 +0200
Final version of ODBC-133 fix and expended test
Revision #16b9541 2018-03-25 19:47:30 +0200
[ODBC-133] Wrong values for bound as NUMERIC type
Revision #d86a5ca 2018-03-22 12:41:19 +0100
[ODBC-137] fix variant. 133 and 139 testcases
Revision #f07b8ff 2018-02-20 05:02:56 +0100
[ODBC-91] The fix and the testcase. If the connection handles was reused, the connector would try to use default database from previous connection (and if there wasn't such database the connect would fail). That happened because connector copied database name form connection string to the structure field where SQL_ATTR_CURRENT_CATALOG attribute is stored, if it wasn't set.
Revision #e0be887 2018-02-14 18:51:30 +0100
Version bump -> 3.0.4
Revision #8cf710f 2018-02-10 19:15:46 +0100
Merge pull request #21 from FaramosCZ/mschorm_1
Revision #8b84d59 2018-02-10 18:41:05 +0100
Fix FSF address
The most recent (GA) release of MariaDB Connector/ODBC is:
Release date: 19 Jan 2017
For the highlights of this release, see the .
The revision number links will take you to the revision's page on GitHub. On you can view more details of the revision and view diffs of the code modified in that revision.
2017-01-17 23:46:20 +0100
Fix of build problems on rhel5.
Revision #b2f32ca 2017-01-17 00:46:27 +0100
MADB_OPT_FLAG_PAD_SPACE was doing what MADB_OPT_FLAG_IGNORE_SPACE is supposed to do. Fixed that + in the setup dialog. Changed FindMariaDB to skip search if directory values are set (in command line parameters).
Revision #766e375 2017-01-13 18:21:55 +0100
Updated dll version to 3.0.0.
Revision #1bf80e2 2017-01-08 23:47:41 +0100
Added one more native error (specific to mariadb_stmt_execute_direct) to be treated as "lost connection" Changed CMakeLists to configure odbc*.ini only if tests directory is present.
Revision #0542505 2016-12-02 14:11:54 +0100
Slightly refined multi-statement query detection - it now allows having semicolons at the end of a single statement. Reset rs columns number before preparing query. Changed a few testcases in error.c to make output more informative
Revision #02bef5f 2016-12-01 17:31:27 +0100
mariadb_stmt_execute_direct is not used in case of params array, since it even doesn't make sense, not talking about problems it causes. Once again fixed code around "where current of" execution - index fields count now added to ParamCount, and deducted after execution (in case of execute_direct). Simpler and no problems with prepare+execute or older servers.
Revision #d777bf8 2016-12-01 01:50:21 +0100
Some more fixes around "WHERE COUNT OF". Fixed params allocation and works in conjunction with DAE
Revision #81d5e44 2016-11-30 16:55:54 +0100
Fixed "where current of" operation - there was error in total parameters count calculation. stmt is now closed and re-ignited before new Prepare on the same handle. Number of pre-bound parameters is set even if it is 0. ParamCount type is changed to SMALLINT.
Revision #e4ac5ec 2016-11-24 00:56:00 +0100
Removed couple of not really needed intermediate functions called by SQLFetch and SQLFetchScroll.
Revision #4242e3c 2016-11-22 11:10:45 +0100
Changed max->MAX, min->MIN. Added more data to generated DSN config in odbc.ini. Added cmake macro to easier populate values (for ini generations so far).
Revision #7d73e86 2016-11-21 17:52:19 +0100
Added ini files generation for testing with UnixODBC Set correct version.
Revision #7cd56ca 2016-11-17 15:01:39 +0100
As ma_errormsg.h has been renamed in C/C back to errmsg.h, had to change its inclusion.
Revision #fbc65f3 2016-11-17 00:30:07 +0200
Some more fixes for build on *nix. Mainly addint defines for TRUE and FALSE does that. Also had to add dl to tests linking list in dirty way. Fixed warnings.
Revision #c5af166 2016-11-16 22:41:01 +0100
Copied code for LIST, DYNAMIC_ARRAY, DYNAMIC_STRING from C/C to enable build on *nix, there my_global.h and my_sys.h are not installed any more, and to eventually make dynamic linking of C/C possible. All types and functions naming patterns have been changed. Also copied some macros, defined in aforementioned headers, and used in either c/odbc or in newly copied code.
Revision #e58af25 2016-11-14 20:52:19 +0100
Support of mariadb_stmt_execute_direct in first approach(ODBC-63).
Revision #ded6696 2016-10-28 00:32:38 +0200
Revision #572bdb1 2016-10-27 19:44:59 +0200
Fix and testcase for ODBC-57. The problem was that MS Access adds parenthesis around each SELECT in the UNION. And the function determining query type wasn't ready for that. Now it skips query string characters till first alpha.
Revision #3f1bb8b 2016-10-21 18:55:37 +0200
Fix of problems with cursors and positional operations. Many things were relying on internal C/C stuff; that has been changed in C/C 3.0. That code had to be refactored. Removed unused fields from one of descriptor structures.
Revision #db232db 2016-10-13 19:31:18 +0200
Enabling build against C/C 3.0
Revision #43c8d5a 2016-08-16 01:02:24 +0200
Fixed some bugs in SQLSetPos with SQL_COLUMN_IGNORE - we had failing test in cursor.c Also fixed error it returns if there were errors on some of the updated rows.
Revision #48bc3e1 2016-10-15 00:31:19 +0200
mysql_stmt_bind_param instead of direct copying of BIND structures to stmt handle property. mysql_stmt_row_tell/row_seek instead of direc MYSQL_ROWS pointer manipulation. Removed couple of TODOs (simple or done). Fixed a bit my_dynamic_pos_cursor1 test.
Revision #0c101a2 2016-10-14 13:22:03 +0200
Changed MADB_CALLOC to follow old ma_malloc (MY_ZEROFILL)) behavior in case of 0 length. Solves many problems comped to simple calloc.
Revision #609489d 2016-10-14 11:13:54 +0200
Fix of crashes caused by relying on C/C internal features, changed in 3.0. In this case that was setting length_value of param bind structure, and not letting length buffer pointer. Older C/C does that, if length is NULL. Changed some helper functions parameters to "const" to avoid warnings, and just because that is right.
Revision #9eab0b8 2016-10-13 19:31:18 +0200
Enabling build against C/C 3.0.
Revision #774a5a9 2016-04-29 14:00:01 +0200
Build with C/C 3.0 enabler.
The most recent Stable (GA) release of MariaDB Connector/ODBC is:MariaDB Connector/ODBC 3.2.5
DownloadRelease NotesChangelogAbout MariaDB Connector/ODBC
Release date: 14 Nov 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 #3eed852 2018-11-13 00:01:24 +0100
Version bump -> 3.0.7 Also, the fix of one compilation warning and of the memory leak introduced by one of fixes in this release
2018-11-09 01:07:26 +0100
, and fixes These are all date/time types related issues. Correct errors, fractional part, type conversions.(overflow errors detection and reporting) was partly done earlier. is mostly fix in C/C, but added similar changes to similar function in c/odbc, and added the testcase.
2018-11-05 23:44:43 +0100
and - fixes and testcases Connector would not return NULL for 0000-00-00 datetime values in case of SQLGetData call, while doing that in SQLFetch. Also it would not do that in case of empty string conversion to date/time types. If time field fetched as timestamp type, fractional part is set to 0. The patch makes SQLFetch and SQLGetData to use the same function to copy data to application buffers and process erroneous values.
2018-10-31 15:13:35 +0100
The fix and the testcase + test The problem was incorrect buffer address calculation for the TIMESTAMP type in case of row-based columns binding. That caused the error in ADO, and could cause a crash. Some issues were fixed along the way. Like caring of the case when value buffer is not provided for the field, or if Indicator and StrLen (for the column) have different buffers.
2018-10-18 00:52:16 +0200
The fix and testcases The main issue was incorrect processing of the connect string with NULL-separated key=value pairs. But also there were found and fixed many issues with ConfigDSN use. Like no dialogs/message boxes should be showed if the parent window handle isn't provided. Extended dsn_test to test ConfigDSN more thoroughly in the interactive mode.
2018-10-13 00:03:03 +0200
Improved the SQLProcedureColumns testcase It would fail if connection charset was not a single-byte
2018-10-10 00:43:37 +0200
Removing C/C auth plugins from packages
2018-10-03 00:41:59 +0200
Last part. Caring of 0-date in the string Enforcing of the constraint on date/time values in case they are passed as a string. Enhanced the testcase for Fixed calculation of the SQL type from the concise type - it didn't consider ODBCv3 types.
2018-10-01 14:31:21 +0200
The fix and the testcase The fix has been accidentally lost in previous commit. In case if SQL_DATA_TYPE value was fetched in the bound buffer, the truncation error would occur. The fix is casting the column in the query to SIGNED type
2018-09-20 15:58:05 +0200
The fix and testcases This is fixes several issues with SQLColumns and SQLProcedureColumns, as they share good part of SQL queries. Most of issues are rather minor.
2018-09-18 17:58:38 +0200
Change requested in - SQL_DATA_TYPE value casted to SIGNED in SQLColumns query. Otherwise its type(returned by server) is MEDIUM_BLOB. Even though at the moment it's not quite clear what is the problem, the change looks reasonable.
2018-09-13 17:48:26 +0200
The fix and the testcase. If data was fetched using SQLGetData, with batches of SELECTS that would fail like described int the bug - empty values or even the program crash. The reason was that in such case one of structures involved in the data fetching was not reset on move to the new resultset. Also the patch fixes SQLRowsCount for batches of upserts or other statements generating affected rows count
2018-09-12 11:34:19 +0200
The fix and the testcase If SQL_TIME field was bound as SQL_C_TIMESTAMP, and the day field was not zero, the inserted time value would be different from the value in time fields of the parameter(server would add total number of hours in those days to the time). The patch makes connector to copy only time fields for the parameter. Also, the patch enforces time and date validity checks for such parameters, as the specs require.
2018-09-11 20:17:54 +0200
The fix + the testcase The crash or error could be caused by error in the (client side) query parsing in case of a dash followed by a string containing newline character and semicolon
2018-09-07 19:51:38 +0200
Optimization for some long queries Optimization is only used for queries longer than 32K. And it skips most of parsing job in case if connector is sure that the query is not a multistatement, and does not have parameters.
2018-09-07 01:24:15 +0200
The fix and the testcase. In case of SP call, if one of its queries resulted in error, connector would not return the error on corresponding result fetch, but would return it as SQL_NO_DATA. Moreover, instead of last result with SP execution status, connector would also do the same. Thus, for example, application could not get affected rows count.
2018-08-11 04:18:19 +0200
Adding BUILD.md file with build instructions
2018-08-09 23:27:28 +0200
Fixed generation of the source package with git.
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 #ed35eb6 2018-02-06 12:55:20 +0100
Added missing dependency in windows build(version.lib is needed by C/C)
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 in some cases with CursorLocation adUseClient
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-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-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-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 as 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-06-22 14:12:19 +0200
correct include guard
2017-12-03 16:25:51 +0100
Adding server to Travis tests. Skipping one test with 5.5 servers(and MySQL <5.7), since it doesn't make sense there.
2017-12-19 19:16:55 +0100
Fix of warning from recent pull request
2017-12-13 10:49:18 +0000
Return correct scale for SQL_C_NUMERIC
2017-11-27 22:32:02 +0100
Fixing remaining issues in Travis Made (most of) testframework 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-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-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
The most recent Stable (GA) release of MariaDB Connector/ODBC is:MariaDB Connector/ODBC 3.2.5
DownloadRelease NotesChangelogAbout MariaDB Connector/ODBC
Release date: 1 Aug 2017
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 #e5dd744 2017-07-31 02:30:34 +0200
[] Starting from v. 10.2.7, server encloses COLUMN_DEFAULT in the table, in single quotes for literal strings. Connector now considers the server version, when constructing the query for SQLColumns .
2017-07-31 01:19:28 +0200
Fix of small error in CMakeLists.txt (addition to previous commit). Fix of possible memleak. Could occur if cursor was closed after a query that did not produce result-set or contain parameters. Pretty extravagant, but it looks like more likely to be the case with UnixODBC.
2017-07-30 19:47:57 +0200
[] Support of MariaDB prepared statements bulk operations.
2017-05-19 02:27:26 +0200
Has all changes from latest 2.0 releases merged
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.