From: Cliff F. <cli...@vo...> - 2004-12-06 11:43:12
|
Colin Draper wrote: > Our problem related to the MySQL ini file being not correctly identified. > In moving from 4.0 to 4.1 it seems that windows requires the MySQL daemon to > be started with an explicit -defaults-file option in order to correctly pick > up the configuration file that pointed to the correct data directory. > Without it, the symptoms were oddly the same, no bugs showing in the > database. I've solved the problem. This morning I went through the upgrade again. This time I did it bit-by-bit, only performing some of the schema updates at a time. The part of the process that threw me was that the upgrade process tries to perform updates from version 0.13 upwards and I was actually running 0.17. So, what would happen is that the upgrade process would try to create tables that already exist and then quit after the first step which was the first failure. Perhaps the upgrade process could be made to be more fault tolerant? Thanks guys for the prompt responses here and on IRC. Regards, -- Cliff Flood Systems Administrator V O X P I L O T +353 1 209 1969 |