About MariaDB Connector/ODBC
MariaDB Connector/ODBC is a standardized, LGPL licensed database driver using the industry standard Open Database Connectivity (ODBC) API. It supports ODBC Standard 3.5, can be used as a drop-in replacement for MySQL Connector/ODBC, and it supports both Unicode and ANSI modes.
Connector/ODBC 2.0 is current stable release series, 3.0 is the new development release series.
The most recent Stable (GA) release of MariaDB Connector/ODBC is:
MariaDB Connector/ODBC 3.2.2
Date | Release | Status | Release Notes | Changelog |
---|---|---|---|---|
19 Jan 2017 | MariaDB Connector/ODBC 3.0.0 | Alpha | Release Notes | Changelog |
23 May 2017 | MariaDB Connector/ODBC 2.0.15 | Stable (GA) | Release Notes | Changelog |
7 Apr 2017 | MariaDB Connector/ODBC 2.0.14 | Stable (GA) | Release Notes | Changelog |
31 Oct 2016 | MariaDB Connector/ODBC 2.0.13 | Stable (GA) | Release Notes | Changelog |
15 Sep 2016 | MariaDB Connector/ODBC 2.0.12 | Stable (GA) | Release Notes | Changelog |
9 Jun 2016 | MariaDB Connector/ODBC 2.0.11 | Stable (GA) | Release Notes | Changelog |
11 Apr 2016 | MariaDB Connector/ODBC 2.0.10 | Stable (GA) | Release Notes | Changelog |
16 Nov 2015 | MariaDB Connector/ODBC 2.0.9 | Beta | Release Notes | Changelog |
11 Apr 2016 | MariaDB Connector/ODBC 1.0.6 | Stable (GA) | Release Notes | Changelog |
10 Sep 2015 | MariaDB Connector/ODBC 1.0.5 | Stable (GA) | Release Notes | Changelog |
29 Jan 2015 | MariaDB Connector/ODBC 1.0.0 | Stable (GA) | Release Notes | Changelog |
2 Apr 2014 | MariaDB ODBC Driver 0.9.1 | Beta | Release Notes | Changelog |
Contents
Obtaining MariaDB Connector/ODBC
The driver is available for download from https://downloads.mariadb.org/connector-odbc/
You should install both the 32-bit and 64-bit drivers. Otherwise you may get this error message:
[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application.
Source code
The source code is available on GitHub: https://github.com/MariaDB/mariadb-connector-odbc
Connection parameters
When configuring a DSN you can use the following keywords:
DSN
: Name of the DSNDriver
: The name of the MariaDB ODBC Driver. Must always be{MariaDB ODBC 2.0 Driver}
Server
: name or IP of the MariaDB database server. Aliases:Servername
User
: user name for database authentication. Aliases:UID
,Password
: password for database authentication. Aliases:PWD
Database
: default database. Aliases:DB
Port
: TCP/IP Port of the database serverOption
: For MySQL Connector/ODBC compatibility. Aliases:Options
NamedPipe
: boolean value(non-zero value is treated as TRUE) determining whetherServer
is treated as a named pipe name, or as domain name/IP address. Using ofNamedPipe
is equivalent of setting/resetting of 13th bit(counting from 0, 8192)OPTIONS
bit. It has effect on Windows only.TCPIP
: has reverse meaning withNamedPipe
. i.e. setting TCPIP=0 effectively means NamedPipe=1. This keyword is also Windows specific.SOCKET
: full socket name, if it is specified, server name is disregarded. It has effect on Linux only.INITSTMT
: SQL command(s) to be run at connection timeCONN_TIMEOUT
: connect timeout in secondsAUTO_RECONNECT
: enabling/disabling automatic reconnect, the same as setting/resetting 22th(4194304)OPTIONS
bitNO_PROMPT
: suppresses prompt dialog display at the connection time.CHARSET
: connection character set. Connector assumes that all incoming (ANSI) string data is encoded in this character set, and uses it if recoding to/from Unicode encodings is required.PLUGIN_DIR
: directory where to look for (Connector/C) plugins.
Example
SQLWCHAR *ConnStr= L"Driver={MariaDB ODBC 2.0 Driver};Server=localhost;UID=odbc_user;PWD=odbc_pw;DB=odbc_test;Port=3306";
Known bugs and limitations
- multiple statement execution is not fully supported
Bug reporting
In case you will find a bug, please report it via the Jira bug system for MariaDB products.
License
GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.
For licensing questions, see the Licensing FAQ.