LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 11-15-2012, 10:32 AM   #1
tronayne
Senior Member
 
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,034

Rep: Reputation: 755Reputation: 755Reputation: 755Reputation: 755Reputation: 755Reputation: 755Reputation: 755
MySQL 5.5 Default Storage Engine


In MySQL 5.5, InnoDB is the default storage engine; previous editions were MyISAM by default.

I have a couple of FOSS LAMP applications that build lots of tables with no engine= directives yet they do full-text searches and
Quote:
If a table relies on some MyISAM-specific feature, you'll receive an error; add the ENGINE=MyISAM clause to the CREATE TABLE statement to avoid the error. (For example, tables that rely on full-text search must be MyISAM tables rather than InnoDB ones.)
(from the MySQL 5.5 Reference Manual, 14.3.1).

I've added
Code:
default-storage-engine=myisam
to the mysqld section of /etc/mysql/my.cnf (which is a copy of the my-huge.cnf file), stopped the MySQL daemon and started (no errors).

Another option is
Code:
skip-innodb
but I'm not real sure which is the better; the default-storage or skip-innodb -- if anybody has any thoughts I'd appreciate knowing them.

I'm going to drop all the data bases and recreate them (well, one anyway) to check with
Code:
SHOW VARIABLES LIKE 'have_innodb';
hoping for a NO but haven't gotten that far as yet.

Any advice on going backwards or if it's worth the effort (a lot of effort, methinks) to deal with InnoDB?
 
Old 11-15-2012, 11:46 AM   #2
tronayne
Senior Member
 
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,034

Original Poster
Rep: Reputation: 755Reputation: 755Reputation: 755Reputation: 755Reputation: 755Reputation: 755Reputation: 755
OK, blew away data bases, reinstalled one application, loaded one not-so-large table set into the data base, thing flies instead of crawls; appears that the default-storage-engine=myisam does that trick (at least for that and I don't have to edit every create table statement in the application).

So, older LAMP applications that relied on MyISAM (the old default) may not work so hot if you just drop and recreate a database without incorporating the default-storage-engine syntax in /etc/mysql/my.cnf or, possibly, skip-innodb and altering all your create table statements (with the proviso that "tables that rely on full-text search must be MyISAM tables rather than InnoDB ones."

Anyway, life is better.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
MySQL and archive Storage Engine varunb Linux - Newbie 4 07-10-2012 03:30 AM
Archive storage engine on mysql varunb Linux - Newbie 2 05-01-2012 11:58 PM
LXer: Sphinx As MySQL Storage Engine (SphinxSE) LXer Syndicated Linux News 0 05-21-2010 07:30 PM
LXer: A Look at the MySQL CSV Storage Engine LXer Syndicated Linux News 0 05-06-2006 04:54 PM
LXer: Soliddb™ Storage Engine for MySQL LXer Syndicated Linux News 0 04-17-2006 10:54 PM


All times are GMT -5. The time now is 02:58 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration