I just noticed that the tiki_acct_* tables are using InnoDB even if MyISAM
is specified as the target engine.
This is probably done to make sure the data remain intact, which would be
required in an accounting system.
I have been unable to locate where the conversion from MyISAM to InnoDB
occurs for the tiki_acct_*.
However, I can see the same thing in several installations, which have been
upgraded to 8.3.
This change may not allow Tiki to be installed, if only the MyISAM engine is
Preventing Tiki usage, where the Accounting module is not needed.
Assuming the InnoDB is "required" for the Accounting module, it may be
better to use the selected database engine,
and give a clear notice to the user that using MyISAM is risky business for
Thus the user should select InnoDB as the target engine (or convert the
database from MyISAM to InnoDB).
Enforcing referencial integrity through the use of foreign keys is not yet
available in Tiki itself,
and should at this moment not be used. The FK concept must be clarified
Get latest updates about Open Source Projects, Conferences and News.