Convert EE's MyISAM to InnoDB?

[Double Negative]

Any particular reason one couldn't convert EE's MyISAM tables to InnoDB?

Such as full-text search fields, or?

[Double Negative]

Well, I converted the tables. Everything seems to work okay. Here's a quick way to do it with Unix:

mysqlshow --user=user --password=password ee | grep ee_ | awk '{print "ALTER TABLE `"$2"` ENGINE=innodb;"}' | mysql --user=user --password=password ee

...Just replace the user and password values as appropriate for your system.

You can go backwards by replacing "innodb" with "myisam" in the above command line.

[Pekka]

EE is mostly about reading data, InnoDB advantage is in row-level locking during writes. So I do not see EE gaining anything significant from it.

[Double Negative]

EE is mostly about reading data, InnoDB advantage is in row-level locking during writes. So I do not see EE gaining anything significant from it.

Yeah, I didn't expect any performance improvement.

Mostly just to consolidate my databases on a specially-mounted filesystem (forcedirectio) so I don't need to separate them. If I leave EE as MyISAM I'd have to move the files to another filesystem as performance would be horrendous otherwise.

Seems to be working great, anyway. :)

[Double Negative]

Just figured I'd drop a quick note to say that EE has been working with converted InnoDB tables for me since I converted them back in March - no issues.