utf8 and mysql

Nice bugs that no one seems to want to fix:- mysql> create table test5 ( wibble varchar(500), PRIMARY KEY (wibble) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin; ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes mysql> create table test5 ( wibble varchar(500), PRIMARY KEY (wibble) ) ENGINE=myisam DEFAULT CHARSET=utf8 COLLATE=utf8_bin; ERROR 1071 (42000): Specified key was too long; max key length is 1332 bytes And even with MySQL 6.

signage failure

Notice this in Cambridge today – looks like a wee fail to me (there was a few more than the two bikes in the picture along the wall outside the college) “Please do not lean cycles against this wall”

textmate

OMG (and other leet things), textmate has built in just about everything, ok probably faster using a real web browser to post a blog, but I’ll have to see how useful the svn and SQL bundles are.

upgrading the playstation 3

Well finally borrowed an USB disk big enough - though the actual backup of the playstation ended up at 8GB it complained about fitting on my USB drive. So aside from a simple backup of the old drive via the XMB tool. Replace the old 40GB 2.5” SATA drive with a nice shiny 320GB model (and then restored from the USB drive) Quite a few guides on the interweb about how to do that, but I’m still slightly shocked that Sony are using standard parts these days!

managing spotlight indexing

Show the status of spotlight on volumes: $ mdutil -sa /Shared Items/Public: Indexing enabled. /Volumes/Time Machine/Shared Items/Backups: Indexing and searching disabled. /Users: Indexing enabled. /Volumes/pool1: Indexing and searching disabled. /Shared Items/Backups: Indexing enabled. /Groups: Indexing enabled. I was receiving a few errors when trying to spotlight for applications (well they didn’t appear) - running $ sudo mdutil -i off / Error, no index found for volume. What worked to fix this for me was to move the main volume into the privacy section of spotlight and reboot (though i’d expect restarting fseventd might have the same effect) and then remove the volume from Privacy, 10 minutes later and disk has re-indexed and spotlight is working correctly.