A week ago we found a workaround for a bug in MySQL Cluster making it impossible to run a management node on MacOS X. Until the bug is fixed, you should use the --nodaemon option for the ndb_mgmd executable. Both MySQL Cluster v6.3 and v7.0 are affected. Currently, I’m starting the management node like this: ( cd /opt/mysql/mysql; ./libexec/ndb_mgmd -f /opt/mysql/config.ini \ --nodaemon 2>/dev/null 1>&2 </dev/null & ) Obviously, you’ll want to change the paths.

What you do when you’re fed up with a script? Right, you write your own. You’ll have to excuse me for the long shell script you’ll find here below, but I’m not going to bother putting it on some download website. It’s a shell script which starts and stops the MySQL server. Indeed, a replacement for the init.d script found in the MySQL distributions. I’m using it personally on my Macs and it’s not supported in any way.

Work says that we need to store sensitive data like email and customer files on some encrypted media. This is a good thing. My laptop has my home directory secured, but I don’t want to encrypt everything on my desktop. The solution to this is to create an encrypted Disk Image (using Disk Utility) and make Mail.app store my email there. This all works great! The problem surfaced this week when I decided it would be good to shutdown my desktop to save energy (which I usually did, but I got sloppy).

Here is a quick way to compile a simple MGM API application. The example will get the state of all nodes in MySQL Cluster and print whether they are connected or not. All this without a Makefile, we just want to have some simple example on Linux to see how it works. It’s basic, maybe, but sometimes useful to just have a peek. Requirements We assume that: you installed MySQL Cluster 6.

You can define a view in MySQL as follows: CREATE VIEW v AS SELECT 'MySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQL'; The above long string might give trouble reading, but ‘MySQLMy.. ’ is 70 characters long. It will work fine, but check out how MySQL stores it (output of SHOW CREATE VIEW): CREATE ALGORITHM=UNDEFINED DEFINER=`root`@`localhost` SQL SECURITY DEFINER VIEW `v` AS select 'MySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQL' AS `MySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQLMySQL` This is where the trouble starts. If you backup your schema using mysqldump, it will get the above definition, but when you restore it, you’ll get the following error: