MySQL Connector/ODBC can be used as an ODBC database driver on multiple platforms, such as Mac OS X, Windows and Linux.
By installing the MySQL Connector/ODBC driver you will be able to connect to any MySQL databases using the ODBC interface.
There are multiple applications which require you to install the MySQL Connector/ODBC, with some of them being Filemaker, ColdFusion, among others.
Installing the MySQL Connector/ODBC on your Mac is easy, you just have to follow a couple of steps. You must extract the archive, copy the two subdirectories to a suitable location and, after that, register with iODBC using the myodbc-installer bundled with MySQL Connector/ODBC.
ODBC is one of the standard APIs that allow you to connect to SQL servers. It includes a large number of data types, error codes and function calls that you can use for developing database-independent tools.
The MySQL Connector/ODBC gives you a native interface for the MySQL database, while fully supporting the MySQL functionality. Some of the supported functions include transactions, unicode compliance and stored procedures.
Here are some key features of "MySQL Connector/ODBC":
- Standard compliant with multiple ODBC versions
- Works on multiple platforms, including Mac OS X and Windows.
- Functionality Added or Changed:
- Implemented the SQL_ATTR_RESET_CONNECTION connection attribute, newly introduced in ODBC 3.8. See the ODBC specifications for details. Currently, the connection attribute is supported by the Unicode driver, but not the ANSI driver.
- Bugs Fixed:
- Calling SQLBulkOperations() without setting SQLSetStmtAttr resulted in a segmentation fault. (Bug #17714290)
- A memory leak occurred when using Connector/ODBC to update the contents of a row. (Bug #17653461, Bug #70662)
- A bad memory access occurred in the ssps_get_out_params function in my_prepared_stmt.c, when a call was made to a stored procedure with any IN parameters coming after the last OUT or INOUT parameter. (Bug #17640929, Bug #70642)
- A memory leak occurred in SQLConnect() when it was invoked after a call of SQLSetConnectAttr() that used the parameter SQL_ATTR_CURRENT_CATALOG. (Bug #17586844)
- A memory leak occurred in SQLSetStmtAttr(), because statement deallocation was missing. (Bug #17441507)
- A segmen...