List:General Discussion« Previous MessageNext Message »
From:Dan Nelson Date:October 23 2003 5:15pm
Subject:Re: Innodb vs myisam
View as plain text  
In the last episode (Oct 24), Chris Nolan said:
> The answer is actually quite simple!
> 
> There are a few reasons:
> 
> 1. Features.
> 
> Each table type has something over the other. While InnoDB has transactions, 
> foreign keys, hot backup capabilities, consistant read and better write
> concurrency (for many situations), MyISAM has FULLTEXT indexes, the
> option of having secondary AUTO_INCREMENT columns, OpenGIS
> data storage (in 4.1 and above) as well as slighly simplified offline backups. 
> Additionally, MyISAM has lower disk space requirements for any given amount 
> of data.

MyISAM also lets you put indexes and tables onto separate disks for
more performance, and supports a compressed read-only format.

-- 
	Dan Nelson
	dnelson@stripped
Thread
Innodb vs myisamTravis Reeder23 Oct
  • Re: Innodb vs myisamChris Nolan23 Oct
    • Re: Innodb vs myisamDan Nelson23 Oct
  • Re: Innodb vs myisamGabriel Ricard23 Oct
    • Re: Innodb vs myisammos23 Oct