Guys,
This is set to milestone 1.3.1 with 1.5 already out. The bug still exists and it is very annoying as using innodb=force is a good method to avoid getting MySQL started with Innodb engine available as it can happen in some cases.
Guys,
This is set to milestone 1.3.1 with 1.5 already out.
The bug still exists and it is very annoying as using innodb=force is a good method to avoid getting MySQL started with Innodb engine available as it can happen in some cases.