InnoDB compliance. Is FULLTEXT index really needed?

[liluxdev]

Joomla 3.1 now enforces tables to InnoDB (when installed from scratch, not in migration)

See:

https://github.com/joomla/joomla-cms/blob/master/installation/sql/mysql/joomla.sql#L85

I think that the time when MyISAM was more performat and available is gone, so consider to permit InnoDB also in K2...

But to permit InnoDB you have to remove the FULLKEY indexes as they are not supported by the engine and declaring them makes impossible an InnoDB conversion:

https://github.com/joomlaworks/k2/blob/master/administrator/components/com_k2/install.mysql.sql#L121

Are them really used? Maybe in the search plugin but now Joomla as a new search engine too, com_finder, which does optimizations, indexing and taxonomy for us.

[kavadas]

Hi. This what we are going to do for the next major release of K2. Right now i think there is no point changing the database structure.

[dgrammatiko]

Lefteris is there a roadmap somewhere? This next version (i guess is 3?) when is it due? I have some code that I want to bring to the project

[fevangelou]

K2 version 3 is still under development. The code will be published here on Github near the end of November 2013. A blog post will be published on getk2.org providing more details within this month.