I see no reason not to move to innoDB, it has many advantages, including stored procedures which Chris brought to my attention last week ... -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS On Wed, Jan 04, 2006 at 11:26:48AM +0100, Paul POULAIN wrote:

I'm working a little on head atm. I'm wondering why we still use myISAM tables in Koha. innoDB tables seems highly better, as, for example, they support foreign keys, and such feature could strenghten the database I think. It also seems innoDB is a little better in perfs.

so, is there a good reason to use myISAM or can I siwtch to innoDB and improve the DB scheme ? -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

Hi paul Happy new year. I'm not sure if innoDB is a good idea. It has better technical features, however It's future is not clear. The company that develops it was purchased by Oracle. Paul POULAIN wrote:

Hello all,

I'm working a little on head atm. I'm wondering why we still use myISAM tables in Koha. innoDB tables seems highly better, as, for example, they support foreign keys, and such feature could strenghten the database I think. It also seems innoDB is a little better in perfs.

so, is there a good reason to use myISAM or can I siwtch to innoDB and improve the DB scheme ?