Using InnoDB MySQL Tables
Since the very start of Simple:Press we have created what is called a Full Text Index on our post and topic database tables. In simple terms, these indices help boost performance for searches. The problem with them is that with the vast majority of hosting companies, this type of indexing can only be created on what are called MyISAM tables. MyISAM is what is called a MySQL ‘engine’.
The main alternative to the MyISAM engine is a newer type called InnoDB. Newer and more efficient – especially on large databases with a lot of users all contending for access. But, except in rare cases, not supportive of Full Text Indexing.
The trade-off is obvious. Improve the performance of searches – traditionally a database intensive and relatively slow procedure . Or improve overall performance and let searches take just that little bit longer. Let’s be honest – we are mostly talking milliseconds here – but with a lot of users on-line and database queries and updates all contending for resources, those milliseconds can start to add up.
There is also the issue that just recently and every now and then we encounter a host who insists that tables be created using the InnoDB engine. So the issue clearly needed addressing.
With the next major update of Simple:Press (version 5.5.0) we will be dropping the need for the full text indexing mechanisms and supporting whatever table engine the server’s MySQL is set to by default. This might be MyISAM. It might be InnoDB. But Simple:Press will work happily on both.
At the same time we will also be releasing a small and simple WordPress plugin that will convert all of the Simple:Press MyISAM tables in your database – to use the InnoDB engine if this is something you prefer.
And I promise the next update post will be of greater interest to perhaps all users as we swing into test mode for our new Child Theme development planned to make display customisation even easier and secure from future updating.