In general I would say that the designers of the InnoDB data storage file system were more concerned with transactional accuracy and row locking than they were with space efficiency.
Here's a good concise (space efficient!) article that explains the details. http://mysqlha.blogspot.com/2009/01/innodb-myisam-and-disk-space_16.html
Mike Copeland
mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
tech: MySQL/MariaDB backend, version 5+
Anybody know why the same field structures but using the Inno engine type causes a table size to be much larger than if it's a MyISAM table type? I do realize the benefits of using InnoDB for transactions, btw.
Just curious why MyISAM smaller, given same structure.
Thanks, --Mike
[excessive quoting removed by server]