Thanks Dmitry. Excellent tip, as always.
Just to mention that as of MySQL 5.0 the default storage engine remains
MyISAM.
Dmitry Dulepov [typo3] thus spake on 2007-09-18 12:08:
> Hi!
>
> Ignatius Reilly wrote:
>> Is it proof-tested to have _all_ tables of InnoDB type (core + ext)?
>
> I use Inn
Hi!
Ignatius Reilly wrote:
> Is it proof-tested to have _all_ tables of InnoDB type (core + ext)?
I use InnoDb for all tables. Generally InnoDb is slower if you need only to
read, so it is worth to have pages and tt_content as MyISAM. But if tt_content
or pages is really big, it is better to ha
Is it proof-tested to have _all_ tables of InnoDB type (core + ext)?
I suppose that would be the effect of a new install with MySQL directive
[mysqld]
default-storage-engine=innodb
Feedback welcome
Thanks
Dmitry Dulepov [typo3] thus spake on 2007-09-18 09:13:
> Hi!
>
> Peter Falk wrote:
>> Some
Hi!
Peter Falk wrote:
> Some of the database tables in typo3 (from v. 4.1) is created as innoDB
> (syslog, fe_session a.m.). Is this a must or is it possible to change
> the tables to MyISAM?
It is not a requirement but there are reasons for this:
- MyISAM locks the whole table for read and wri
Hi Peter,
I'm not sure, but i guess u can change them to MyISAM. I have a site
that uses all MyISAM tables, and another that has those innoDB tables,
both works.
Btw, I suggest you to not change them. Here you can read why:
http://typo3.org/development/articles/release-notes-41/page/3/
Bye!ian
Some of the database tables in typo3 (from v. 4.1) is created as innoDB
(syslog, fe_session a.m.). Is this a must or is it possible to change
the tables to MyISAM?
Regards
Peter Falk
___
TYPO3-english mailing list
TYPO3-english@lists.netfielders.de
htt
