yes I'm aware, it is why I made the comment about change
However still subject to corporate policy which means sticking with
mysql until they screw up on regular basis, so if they fail to fix
this by next version, I can take it to CIO and present my case, two
deliberate broken versions when fix ma
Hi Nick,
It seems it is fixed already in MariaDB:
http://bugs.mysql.com/bug.php?id=68999
"[9 Jun 9:34] Michael Widenius
This was fixed in MariaDB 5.5 in May 2013 as part of our merge of
MySQL 5.5 to MariaDB 5.5."
Cheers
Claudio
2013/6/9 Nick Edwards
> This was reported in 5.5.31, a patch,
