CODEWITHSUNDEEP
phpmysqlpdoinnodbmyisam
Chuck Le Butt
Chuck Le Butt

Reputation: 48826

InnoDB versus MyISAM

In my particular situation I have a small website of about 6000 registered users. The FK constraints of InnoDB are useful to ensure data integrity, but I'm not sure what other benefits there could be... Especially since I'm losing out on FULLTEXT search, which could be very useful for me.

Is it worth changing my tables over to MyISAM in order to make use of FULLTEXT, or are there other benefits of InnoDB that mean I should make do with my LIKE %keyword% search solution?

(Note: The site is hosted on shared hosting, and so I don't think 3rd party search solutions like Sphinx are viable.)

Upvotes: 3

Views: 1430

Answers (2)

hjpotter92
hjpotter92

Reputation: 80653

Instead of referring to wiki or other pages for comparisions, check their(MyISAM and InnoDB) limitations on dev.mysql.com

Limits on InnoDB Tables

As for MyISAMs limitations, they are mostly on disk/column sizes.

  1. Large files up to 63-bit file length are supported.
  2. There is a limitation of 264 (1.8 * 1019) rows in a MyISAM table.
  3. The maximum number of indexes per MyISAM table is 64.
  4. The maximum number of columns per index is 16.
  5. The maximum key length is 1000 bytes.

InnoDB is pretty much newer and has more support from MySQL team, so using it for smaller and easily recreatable/restorable tables is what I am practising right now. Datas which are more frequently updated/inserted still use MyISAM on my own server.

Upvotes: 2

Kenny Cason
Kenny Cason

Reputation: 12328

According to this link, InnoDB does now support Full Text Search

http://blogs.innodb.com/wp/2011/07/innodb-full-text-search-tutorial/

(note) I'm going to have to read through this a bit more as well, but should be an interesting read none the less.

Upvotes: 1

Related Questions