mISAM vs innoDB

M

midrange

Senior Member
Joined
Apr 8, 2009
Messages
727
Reaction score
0
I always use innoDB as it allows foreign keys (I may be outdated here). All PHP devs on this site seem to use myISAM.

This isn't a question as much as a a request for advice.
 
Last edited:
We are moving away from myISAM as it does not support transactions and partitioned tables which is a limiting factor for us. Besides that, I am not too sure.
 
I heard backing up an innoDB is troublesome.

Edit: Well, extracting the correct data is.


CMSs like Drupal, Joomla, Worpdress all use myISAM.
 
Last edited:
innoDB is perfect for replication and some nice python tools for backups. we usse innoDB engine on 50+ db servers without ever a hitch
 
The major difference between innodb and myisam is that myisam locks the entire table while innodb does row locking.

The benefit of using either/or is up to what your needs are really. myisam has really fast access to data AFAIK when compared to innodb while innodb has compression (?I think?) including other stuff as mentioned. You can also mix your tables within the same database. I haven't gone into the performance aspect between the two but I know some guys running 20+million rows in a table are switching to innodb
 
Thanks for the replies.

I'm about to start a full-time position after a while of freelancing, but will be managing the whole thing. Python has so much appeal to me. I do like .NET though, but when the deadline is short I'm going to be smashing it out in PHP.

(Please never buy an Asus laptop)
 
Still no native support for foreign keys on myISAM?

[/threadjacks own thread]:
Was reading up on RoR the other day and they don't support composite primary keys. I don't think they really know what a primary key is.
 
Last edited:
never asked this question,..... Hibernate answered it for me long before I ever could.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X