yehster wrote on Friday, May 17, 2013:
For future additions, I propose that we don’t include the “ENGINE=xxxx” line in the SQL.
This way, tables will get created with whatever the given MySQL installation is set to use.
If a table specifically needs a feature of a particular engine, (e.g. FULLTEXT indexes only work with MyIASM last time I looked…) it can still be included, but there’s really no good reason to force one engine or another at time of creation.
bradymiller wrote on Wednesday, May 22, 2013:
Hi,
This doesn’t seem like a good idea. Seems like setting this explicitly to something makes it much simpler to upgrade to innodb in the future in addition to avoid needing to test code on both a innodb/myiasm default database(hard enough to keep compatibility on different php version, much less different storage engines). Here’s a entry on differences:
I haven’t researched it much, but still seems like the hangup is still the inability to index the TEXT fields.
-brady
OpenEMR