kj wrote:
Hi guys,

Thanks for all the suggestions. It turns out rolling back to MySQL 5.0.x solves the problem. I guess I'm affected by something in 5.1 - just don't know what.

--kj


Perhaps something Monty has discussed: http://monty-says.blogspot.com/2008/11/oops-we-did-it-again-mysql-51-released.html

Cheers,
Steve

Reply via email to