MySQL Connector/ODBC

MySQL Connector/ODBC for MAC – Connect MySQL server to ODBC database API. This app was released by MYSQL Inc. and yesterday updated into the last version. Download this Internet Utilities app for free now on ForMacApps.com

 

MySQL Connector/ODBC for MAC Latest Version

MySQL Connector/ODBC for Mac: Free Download + Review [Latest Version]. Before you download the .dmg file, here we go some fact about MySQL Connector/ODBC that maybe you want to need to know.

App Name MySQL Connector/ODBC App
File Size 4.1 MB
Developer MYSQL
Update 2014-04-09
Version 5.3.2
Requirement Mac OS X 10.6.8
License FreeWare


MySQL Connector/ODBC icon

 

About MySQL Connector/ODBC App for MAC

MySQL Connector/ODBC (also known as MyODBC) allows you to connect to a MySQL database server using the ODBC database API on all Microsoft Windows and most Unix platforms, including through such applications and programming environments such as Microsoft Access, Microsoft Excel, and Borland Delphi.

New Features

Version 5.3.2:

Functionality added or changed:

  • Support of ODBCINSTGetProperties in MyODBC Driver (WL #7577)
  • Add DFLT_BIGINT_BIND_STR option to Connector/ODBC GUI (Windows and Linux)
  • (WL#7579)
  • Accessibility features in Connector/ODBC Linux GUI (WL #7635)

Bugs fixed:

  • Connect crash if the catalog name given to SQLSetConnectAttr is invalid (Bug #17587913)
  • Driver returns wrong length for output parameter streams (Bug #17814768/70946)
  • Assert failure in case of prepared statments and SQLDESCRIBECOL() called with column number given larger then actual parameter marker in query. (Bug #17311065)
  • SQLFOREIGNKEYS WITH FLAG_NO_INFORMATION_SCHEMA OPTION RETURNS BAD RESULTS (Bug #16920750)
  • SQLFetch() crashing when execute using UnixODBC 2.3.2 (Bug #17857204)
  • Segmentation fault in SQLSpecialColumns if table name is invalid (Bug# 17854697)
  • Invalid order of free() functions can cause crash (Bug# 17992912)
  • Crash in ODBC Driver with CHARSET=WRONGCHARSET (Bug# 17999659)
  • Driver and myodbc-installer crash with long option names (>100) and values (>255) (Bug# 17966018)
  • ODBCManageDataSourcesQ4 cannot run MyODBC GUI setup to edit an existing
  • DSN (Bug# 18046123)
  • SQLGetData returning error being called after SQLParamData (Bug #17842966)
  • Valgrind: jump or move depends on uninitialised value error from myodbc-installer (Bug# 18046120)
  • Memory leak in sqlexecute() when connection is killed from another thread (Bug#17587617)
  • Data corruption in SQLBulkOperations because of buffer overrun. (Bug #17714172)
  • Segfault in SQLBulkOperations() for SQL_UPDATE_BY_BOOKMARK when select returns 0 records. (Bug# 17714358)
  • MS Access crashed when sorting a column (Bug# 17071780/69550)
  • Empty query giving segmentation fault in myodbc_casecmp (Bug# 17085344)
  • Uninitialized variable free_value can set wrong error in SQLDescribeCol (Bug# 17588101)
  • ODBC 5.2.5 DMG installer fails on OSX 10.8.5 (Bug #17512040/70422)
  • Bulk insert on time column with hour value > 99 gives error (Bug#17613161)
  • Concurrent execution of SQLEndTran() with SQL_HANDLE_ENV results in SEG FAULT (Bug #18166331)
  • Workaround to GTK bug in GtkComboBox and GtkComboBoxEntry (WL #7637)
  • ODBC Driver GUI in Windows has wrong order of controls selection (Bug# 18240696)
  • Wrong installation library directory on some 64bit system other than x86_64. (Bug# 68848)
  • SQLNumResultCols() with NULL parameter results in Segmentation Fault (Bug# 18165197)
  • SQLBULKOPERATIONS(SQL_FETCH_BOOKMARK) RETURNS SQL_NO_DATA ERROR (Bug# 18287216)
  • Segmentation Fault in SQLExecute() while executing test file “my_types” (Bug# 18303978)
  • Segmentation fault in SQLParamOptions() in Solaris platform (Bug# 18325878)
  • Segmentation fault in SQLForeignKeys() when number of columns in the table is more (Bug# 18286366)
  • Valgrind memory leak in SQLForeignKeys when NO_I_S=1 (Bug# 18286007)
  • Valgrind memory leak in when SQLPrepare used with SQLParamData/SQLPutData for NO_I_S=1 (Bug#18295317)
  • The password is getting saved when creating FileDSN using SQLDriverConnect (Bug# 18310873)
  • Passing NULL pointer to SQLSetDescField, SQLGetDiagField and SQLGetDiagRec results in a crash (Bug# 18431088)
READ ALSO Recommended Apps:   sshOpener

Installing Apps on MAC

Most Mac OS applications downloaded from outside the App Store come inside a DMG file. Like if you wanna download MySQL Connector/ODBC for mac from this page, you’ll directly get the .dmg installation file into your MAC.

  1. First, download the MySQL Connector/ODBC .dmg installation file from the official link on above
  2. Double-click the DMG file to open it, and you’ll see a Finder window.
  3. Often these will include the application itself, some form of arrow, and a shortcut to the Applications folder.
  4. Simply drag the application’s icon to your Applications folder
  5. And you’re done: the MySQL Connector/ODBC is now installed.
  6. When you’re done installing: just click the “Eject” arrow.
  7. Then you can feel free to delete the original DMG file: you don’t need it anymore.
  8. Now, enjoy MySQL Connector/ODBC for MAC !

You don’t have to put your programs in the Applications folder, though: they’ll run from anywhere. Some people create a “Games” directory, to keep games separate from other applications. But Applications is the most convenient place to put things, so we suggest you just put everything there.

DMG files are mounted by your system, like a sort of virtual hard drive. When you’re done installing the application, it’s a good idea to unmount the DMG in Finder.
 

Uninstall Apps on MAC

Removing MySQL Connector/ODBC apps is more than just moving them to the Trash — it’s completely uninstalling them. To completely uninstall a program on MacBook/iMac, you have to choose one of the options on below.

Method 1: Remove apps using Launchpad

Another manual way to delete MySQL Connector/ODBC apps from your Mac is using the Launchpad. Here’s how it works:

  1. Click Launchpad icon in your Mac’s Dock.
  2. Find the MySQL Connector/ODBC that you want to delete.
  3. Click and hold the MySQL Connector/ODBC icon’s until it starts shaking.
  4. Click X in the top-left corner of the app icon.
  5. Click Delete.

Method 2: Delete MAC apps with CleanMyMac X

Now it’s time for the safe and quick app uninstalling option. There’s a safest way to uninstall MySQL Connector/ODBC on Mac without searching all over your Mac, and that’s by using CleanMyMac X.

  1. Launch CleanMyMac X and click on Uninstaller in the left menu.
  2. Select the , you can either uninstall it or, if it’s not acting as it should, you can perform an Application Reset.
  3. Click on Uninstall or choose Application Reset at the top.
  4. Now that the application cleanup is complete, you can view a log of the removed items, or go back to your app list to uninstall more.
  5. And you’re done to remove MySQL Connector/ODBC from your MAC!

 

MySQL Connector/ODBC Alternative App for MAC

Here we go some list of an alternative/related app that you must try to install into your lovely MAC OSX

 
DISCLAIMER
This MySQL Connector/ODBC .dmg installation file is absolutely not hosted in our Server. Whenever you click the “Download” button on this page, files will downloading directly in the owner sources Official Website. MySQL Connector/ODBC is an app for MAC that developed by Inc. We are not straight affiliated with them. All trademarks, registered trademarks, product names and company names or logos that mentioned in right here would be the assets of their respective owners. We’re DMCA-compliant and gladly to cooperation with you.