CMS MADE SIMPLE FORGE

CMS Made Simple Core

 
Back Back to List

[#8684] type MyIsam

avatar
Created By: delaunay (pierrepercee)
Date Submitted: Wed Nov 28 07:32:27 -0500 2012

Assigned To:
Version: None
CMSMS Version: None
Severity: Minor
Resolution: Fixed
State: Closed
Summary:
type MyIsam
Detailed Description:
The engine type (MyIsam) is not specified when installing CMSMS. Since
Wampserver 2.2, the tables are created sometimes with the MyIsam type, sometime
for a few tables with Innodb type. It could be very long when CMSMS create the
tables during the installation.
More than that, when you export the database and import it in a online site ,
you can't access to "Maintenance system" :
Fatal error: Call to a member function FetchRow() on a non-object in
/homez.xxx/www/admin/systemmaintenance.php on line 246


History

Comments
avatar 
Date: 2012-11-28 23:07
Posted By: Fred Polizo (fredp)

For what it's worth..  I noticed this behavior earlier this year, but found a
simple workaround that might work for you, if you have write access to your
MySQL server config: make MyIsam the default storage engine for your MySQL
server. Not perfect, since it is a server-wide change. In my case, though,
that's not a problem; so, I just appended this line to my server's  /etc/my.cnf
and restarted the server:

default-storage-engine = MyISAM

...in case it helps.
avatar 
Date: 2012-11-29 06:07
Posted By: Jean-Marc Lerouge (jeanlechauve)

Tables are also modified to InnoDB when you run upgrade.php
The snapshot (OVH) don't work with InnoDB.
More than that : InnoDB doesn't support FULLTEXT indexes
avatar 
Date: 2012-11-29 11:15
Posted By: Robert Campbell (calguy1000)

Fixed in SVN.  Needs significant testing for new installs and
uninstall/re-install of modules when using mysqli driver particularly.

We now specify default table options for mysql and mysqli drivers if none are
specified to set engine to MyISAM.
If no collation or charset table options are specified we append UTF-8 charset
and collation options.
avatar 
Date: 2012-11-29 13:35
Posted By: Robert Campbell (calguy1000)

Technically this wasn't a 'bug'.   as the core neither uses full text indexes
(MyISAM) or transactions (InnoDB only IIRC).  Therefore the table format
shouldn't really matter.   The fact that InnoDB appears to be dramatically
slower on a WAMP environment (for some people).  is not technically a CMSMS
issue.

CMSMS does NOT explicitly modify the table format on upgrade.  This may be
something inside the mysql environment.
Updates

Updated: 2012-12-01 10:23
state: Open => Closed

Updated: 2012-11-29 11:40
resolution_id: 5 => 7

Updated: 2012-11-29 09:11
resolution_id: => 5
severity_id: 2 => 3