My personal opinion is that we give the users a choice between InnoDB and MyISAM. There are a number of reasons (although fewer by the day) that some users may still want to use MyISAM - One example of this is that InnoDB tables are inherently larger, very noticable on scaling installations...
I do however agree that InnoDB should be the default as it carries the least performance overhead in the long run and could save a lot of headaches. Cheers, Kenny. On 17 April 2012 23:52, Daniel Danger <[email protected]> wrote: > Hi, > > I'd like to propose that we switch to innodb as a database engine for > owncloud (when using mysql as a database). > The reasons for my proposal are: > - support for foreign keys > - should perform better (especially in large setups) > - will be the default in newer versions of mysql anyhow [1] > > I know that some webhosters only support php4, so there might be some > out here which don't support innodb. In that case I would suggest that > the people use sqlite or switch to a different webhoster ;) > Anyhow, does anyone of you know a (popular) webhoster that does not > support innodb? And do we therefore really have to care? > > Any comments on this? > > Regards > Daniel > > Ps.: Sorry for the harsh words about old software. > > > [1] http://dev.mysql.com/doc/refman/5.5/en/innodb-default-se.html > _______________________________________________ > Owncloud mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/owncloud >
_______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
