MyISAM vs InnoDB tables

Dear All,

Is there a reason why ODK tables are MyISAM and not InnoDB (or maybe there were an option while configuring aggregate?). Can we change/convert existing tables to InnoDB without any problems?



1 Like

DISCLAIMER: I have not tested so it's hard to know for sure

Yes I believe you should be able to switch between them as Aggregate is designed to work on multiple database backends including PostGres, MySQL, BigTable, etc. Therefore, changing the underlying implementation of MySQL should have little effect since Aggregate is designed to not take advantage of any platform specific optimizations and instead tries to utilize generic constructs shared by all databases. Unfortunately, the only way to know for sure is to test it.

Thanks, will test it out.

This is incorrect.

As of MySQL 5.5.5, the default storage engine is InnoDB.

If memory serves, the TaskLock implementation cannot run on a MyISAM volume; it requires InnoDB.

The rest of the server design operates without transactions, so it could potentially work on MyISAM.