List:General Discussion« Previous MessageNext Message »
From:Brent Baisley Date:August 16 2008 12:52pm
Subject:Re: another INNODB vs MYISAM question
View as plain text  
First, databases do not have a table type, they are mainly just a  
logical grouping of tables. Mixing table types in a database is quite  
alright and is what you are supposed to do. I generally use MYISAM,  
but if I have a table with lots of activity (inserts, deletes,  
selects) or needs transaction support, I use InnoDB.

What you did was not only switch the default table type, but you  
disabled the InnoDB table type. As you may already know, MySQL's table  
types are different engines that are really plug-ins. You can disable  
those plug-ins if you like, which is what you did. Just re-enable the  
InnoDB stuff and you should be alright. You can leave your default  
engine as MYISAM and if you like, you can use ALTER TABLE to convert  
your InnoDB tables to MYISAM.

Brent Baisley

On Aug 15, 2008, at 1:01 AM, mikesz@stripped wrote:

> Hello mysql,
> As I have previously mentioned, I installed WAMPSERVER 2.0 on my
> Windows XP pro box recently. It installed INNODB as the Default
> Engine.
> All of my legacy Databases are MYISAM and after the installation, I
> copied them all into the DATA folder and everything worked, even
> adding new tables etc. but the new stuff was INNODB. So I ended up
> with some MYISAM databases that contained INNODB tables in them.
> After a few weeks I got to thinking that mixing INNODB and MYISAM
> might not be a good thing and switched the Default Engine to MYISAM in
> my.ini file. I didn't just switch the default, I commented out all the
> INNODB calls in the my.ini file as well.
> As I half expected, all the databases that I had added INNODB tables
> failed when I tried to fire up the applications that used them.
> Although I am not new to mysql, I have had a bit of MYISAM "tunnel
> vision" with it so my question is, if I had just switched the default
> engine and NOT disabled the INNODB calls in my.ini, would that have
> prevented the "problem"? I restored all the MYISAM files and got
> everything back working again.
> I don't want to go through the "lengthy" reproduction exercise of
> reinstalling everything to test the theory so if someone has had some
> experience with this, I would appreciate hearing from them.
> -- 
> Best regards,
> mikesz                          mailto:mikesz@stripped
> -- 
> MySQL General Mailing List
> For list archives:
> To unsubscribe:

another INNODB vs MYISAM questionmikesz15 Aug
  • Re: another INNODB vs MYISAM questionDoug Bridgens15 Aug
  • Re: another INNODB vs MYISAM questionBrent Baisley16 Aug
    • RE: another INNODB vs MYISAM questionMartin Gainty16 Aug