How to add calendar in outlook mail windows. A guide to setting up a Ruby on Rails development environment on Mac OS X 10.12 Sierra with Git, MySQL, and PostgreSQL. A guide to setting up a Ruby on Rails development environment on Mac OS X 10.12 Sierra with Git, MySQL, and PostgreSQL. Skip to main content. Tutorial Series.

I recently installed MySQL 5.7.2 on macOS High Sierra 10.13.1. I also installed the most recent iODBC Administrator 3.52.12 and the MySQL Connector ODBC 5.3.9, using the package installer. After setting up a test database in MySQL and verifying that it all works well using MySQL Workbench, and setup a user DSN in iODBC Administrator for that database.

The iODBC test of the DSN fails with: IM003 [iODBC][Driver Manager]Specified driver could not be loaded If I move the driver files from: [/usr/local/mysql-connector-odbc-5.3.9-macos10.12-x86-64bit/lib/] to [/usr/local/lib], I get the previous IM003 error followed by this additional error: 00000 [iODBC][Driver Manager]dlopen(/usr/local/lib/libmyodbc5a.so, 6): no suitable image found. Did find: /usr/local/lib/libmyodbc5a.so: mach-o, but wrong architecture /usr/local/lib/libmyodbc5a.so: stat() failed with errno=17 I wonder if there's a solution to this?

Having upgraded to 12 from 11 a few days ago I've decided to revert back to 11, the problems with 12 include: it is very, very slow which I find odd as one of the new 'features' was a faster engine? Editing any record on a remote DB in 11 was immediate on 12 it take minutes as the cursor whirls away secluding plain just doesn't work it crashes for no repeatable reason keyboard commands such as cmd. (and many others) which used to disconnect no longer function pervious working SSH connections fail and quite a bit more, it's very disappointing and I'll think I'l wait for the bugs to be ironed-out as it's frankly unusable. I installed version 12 one day before going on holiday for two weeks, came back to find out the automated backups all crashed during my vacation, a lot of http tunneling connections don't work anymore. The Export Tunnel Script doesn't work etc etc. This is a disappointing piece of (untested) garbage, I haven't seen a version that's been so bad during 10 years of Navicat use.

And what frightens me most is that this version is already at 12.0.7. What did you do Peter? I want to revert to version 11, did you do that too and did you have any issues reverting? Did you open a support ticket like I did? It is important to let Navicat now they are on the wrong track here. I use a lot of software to do my work but I have seldom seen so many bugs in a new version of a good working version.

And yes I understand that a new version always introduces some (minor) bugs. But now complete parts of the functions don't work anymore. Backing up databases crashes Navicat repeatedly.

In addition: 1) export import of connections - not save groups. Ok, but it not easy to sort 130 connections again 2) ok, 130 connections - it is historic for couple of years, so ok - it good time for delete something (but still - 62 active) - but navicat never allow select few connections and move/delete them - again pain 3) but it not all - after restart it lost half of groups.:-) 4) code completion - not work. Tables names not showing, columns not showing 5) queries - not save (it ask, but nothing saved after) 6) external editor do not start I of course not delete 11, so it look like early alfa preview but not final product. Fresh looks, many interesting new features. But most of them - not work now.

I have similiar issues with Navicat 12.0.10 running on Linux. 1) ssh tunnellling is broken. It works for some existing connections but not for others.

This seems completely random. For the ones it doesn't work with, it produces the error: 'Unable to load key'. The key location or file hasn't changed at all. I can't add new connections as they all get the 'Unable to load key' error. 2) Random crashes occur frequently 3) Code completion under Linux is awful.

It is so slow at looking anything up that I have turned it off completely. For example, I open a query and type 'S' and the code completion dialogue opens but is blank. It remains blank for 3 - 5 seconds. It does get better but this shouldn't happen. Code completion works fine under Windows. 4) Opening the first query window after opening Navicat takes ages regardless of how long Navicat has been running.