installing msql 5.0 into instant rials - InnoDB error

rubyonrails-talk
1

Hi Im using a book based on 1.2* ruby and rather than using instal rails to install all req. software it asks the user to do everthing individually. Well i already had instant rails working fine so thought id stick to it. The book wanted msql 5 to be installed and then select various options i.e. set password, internatinal character coding etc via the mysql windows config interface (rather than the command prompt.) To do this I installed msql into instantrails/mysql/ as per the instructions on instant raisl website.

However when i restart instantrails msql spits out an error whilst tring to start and after looking at the logs it says this

InnoDB: Error: log file .\ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 10485760 bytes! 081024 19:09:14 [ERROR] Default storage engine (InnoDB) is not available 081024 19:09:14 [ERROR] Aborting

081024 19:09:14 [Note] C:\INSTAN~1\MySql\bin\mysqld.exe: Shutdown complete

Ive tried reinstalling and changing various options but no luck. I did try installing it outside of instant rails and it worked fine.

Do i have to install it under instant rails if i use IRs command prompt for rails projects?

2

Sorry I made a mistake that should have read a book based on rails 1.2*

3

Sounds like your version of mysql was compiled without support for innodb.

Fred

4

Sounds like your version of mysql was compiled without support for innodb.

Fred

hmm i am using a version that came with the book - its version 5 though. Ill try downloading it direct from the msql website. Why does mysql work fine when i install the same version outside of the IR directory?

5

Sounds like your version of mysql was compiled without support for innodb.

Fred

hmm i am using a version that came with the book - its version 5
though. Ill try downloading it direct from the msql website. Why does mysql
work fine when i install the same version outside of the IR directory?

The configuration file, or the way the mysql server is launched can
also do this sort of stuff, ie if the configuration file tried to do
stuff with innodb settings but the server was launched with the option
that turns off innodb support then you would probably also get that
error.

Fred