MySQL Forums
Forum List  »  InnoDB

Why does my 4.1.9 behave so unusually with InnoDB
Posted by: andy malycky
Date: June 07, 2005 11:20PM

- I installed 4.1.9 in Feb '05
- used the config utility to set params and install as a service
- it selected mysqld-nt as the binary to run by default (I am on XP)
- I created a bunch of innoDB tables (mysql administrator shows them as innodb)
- tables seem fine, but I cannot set autocommit=0, it remains 1
- I cannot set a transaction and rollback, it always commits
- mysql administrator-configure service shows support for innodb checkbox as off
- if I check the box the path to binary turns red!!!
- if I change the binary to mysqld and apply changes the server subsequently fails to start!!!

I then start to get the error
> InnoDB: Error: log file ./ib_logfile0 is of different size
> InnoDB: than specified in the .cnf file!

- I don't have a c:\my.cnf !!! just a my.ini
- changing back to mysqlnt.exe still gave me the error

I reran the config utility , dropped the service, recreated with the config utility and am back up running, but still with mysqld-nt!!!

Doesn't mysqld-nt support innoDB transactions?
If not then why can I create innoDb tables?
Why does the path to binary turn red?
How do I get the support for InnoDb turned on with the proper binary that starts?
Shouldn't I be able to turn off autocommit?
Is there a bunch of special setup needed to use transactions?

What is going on???

Please help me if you have been experiencing similar frustration or know what is going on!!!


Options: ReplyQuote

Written By
Why does my 4.1.9 behave so unusually with InnoDB
June 07, 2005 11:20PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.