Joomla Templates Club 406,261 posts

[gammx1 Friend gammx1Join date: April 2007Posts: 13Downloads:0Uploads:0 Thanks: 5]

#190629

Hi,

>> Joomla! 3.1 default is being installed as InnoDB tables (outside the two ones installed as MEMORY)
>> I saw, as per the included mysql.sql installation file, you forced ja_elastica quickstart to be installed as MyISAM tables…

The problem I’m seeing is if eventually upgrading later to Joomla! 3.2-Alpha then we will get a mix of MyISAM and InnoDB tables

QUESTION: Did you that change (forcing MyISAM for all tables) for any reason or is it a bug? Surely you have a good reason to did it… Could you explain why?

If it Is a bug… I have no problem to repair its default installation as follows:

>> What I’m doing is to use the following 2 steps to change MYSQL DB’s from MyISAM to InnoDB engine through PhPMyAdmin:

Step 1) Run this SQL statement (in the mysql client, phpMyAdmin, or wherever) to retrieve all the MyISAM tables in your database. Replace value of the ‘yourDBname’ variable with your database name:

SET @database_NAME = ‘yourDBname’;

SELECT CONCAT(‘ALTER TABLE ‘, table_name, ‘ ENGINE=InnoDB;’) AS sql_statements
FROM information_schema.tables AS tb
WHERE table_schema = @database_NAME
AND `ENGINE` = ‘MyISAM’
AND `TABLE_TYPE` = ‘BASE TABLE’
ORDER BY table_name DESC;

Step 2) copy the SQL statement output and run it as a new SQL query htrough PhPMyAdmin and your yourDBname

Partial output example (something like):
…
ALTER TABLE pr3f1x_finder_links ENGINE=InnoDB;
ALTER TABLE pr3f1x_finder_filters ENGINE=InnoDB;
ALTER TABLE pr3f1x_extensions ENGINE=InnoDB;
ALTER TABLE pr3f1x_core_log_searches ENGINE=InnoDB;
ALTER TABLE pr3f1x_content_rating ENGINE=InnoDB;
ALTER TABLE pr3f1x_content_frontpage ENGINE=InnoDB;
ALTER TABLE pr3f1x_content ENGINE=InnoDB;
ALTER TABLE pr3f1x_contact_details ENGINE=InnoDB;
ALTER TABLE pr3f1x_categories ENGINE=InnoDB;
ALTER TABLE pr3f1x_banner_tracks ENGINE=InnoDB;
ALTER TABLE pr3f1x_banner_clients ENGINE=InnoDB;
ALTER TABLE pr3f1x_banners ENGINE=InnoDB;
ALTER TABLE pr3f1x_associations ENGINE=InnoDB;
ALTER TABLE pr3f1x_assets ENGINE=InnoDB;

But I would like to know your expert opinion about that, before to proceed,

Thanks in advance your attention & quick feedback
Rgrds,

[Saguaros Moderator SaguarosJoin date: September 2014Posts: 31405Downloads:237Uploads:471 Thanks: 845 Thanked: 5346 times in 4964 posts]

#506283

Hi gammx1,

You’re right, Joomla 3 uses InnoDB engine, I will report this to dev team and will update database for the upcoming release. At this moment you can change engine from MyISAM to InnoDB as you desire.

Thanks for your report.

[Author]

Posts