Re: InnoDB problem with windows MySQL 5.0.15?
Posted by:
Rob Vieira
Date: November 10, 2005 04:08PM
Besides out and out removing the skip-innodb command from the .ini to see if that helps, also be sure to check the entire search path for MySQL. For example, MySQL used to always use my.cnf found in the root of C: as it's config item. You then got the ability to use my.ini if there was no my.cnf. Beginning somewhere in 5.0 (I can't say the full history, as I just saw it when I saw it), the search order began going backwards of the old behavior. If there is an .ini in the MySQL directory, it will get used first. If not, then the my.ini in the Windows system directory, and if that isn't there, then it will go to my.cnf.
Subject
Views
Written By
Posted
45132
November 10, 2005 03:35PM
Re: InnoDB problem with windows MySQL 5.0.15?
6501
November 10, 2005 04:08PM
4515
November 10, 2005 07:50PM
3873
November 11, 2005 05:18PM
3631
November 11, 2005 08:25PM
3428
November 13, 2005 11:47PM
3217
November 14, 2005 01:24PM
7166
November 15, 2005 10:59PM
2870
October 30, 2006 01:32AM
2574
November 18, 2005 07:13AM
2388
November 18, 2005 12:02PM
2488
November 19, 2005 02:44AM
3173
November 21, 2005 04:42AM
9649
July 26, 2006 11:52AM