Re: [Tiki-devel] In a InnoDB populated database the indexes are MyISAM

Hello Bernard,


I am not a Tiki expert but I have some understanding of MySQL and MariaDB.

In MariaDB, the storage engine is defined at the table level which means 
that a database can use different storage engines. The storage engine 
defined at the database or server level is the default storage engine 
that will be used during the creation of a new table. So it appears to 
be a standard behaviour to find some tables with the MyISAM type even if 
you have installed MariaDB with InnoDB as default table storage engine.

Compared to InnoDB, MyISAM has a 2x/3x smaller disk footprint, is faster 
on read and supports full-text indexing, so it appears to be the 
appropriate choice for the "index_xxx" tables from the moment when 
queries on these tables are mostly read/select queries.


Vincent


Le 06/11/2021 à 10:41, Bernard Sfez via TikiWiki-devel a écrit :
> Hello,
>
> Forgive my ignorance about this but it’s been a while I wondered 
> without asking.
>
> I use MariaDB and set or install Tiki with InnoDB.
> However the indexes created by Tiki are MyISAM.
>
>
> That’s the way it should be ?
> Does it have any incidence ?
>
> Bernard
>
>
> _______________________________________________
> TikiWiki-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

_______________________________________________
TikiWiki-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel