Forcing InnoDB as the storage engine

[GoogleCodeExporter]

It's not a defect, just a suggestion: looking at the create table statements, 
you are creating the tables on MySQL with the default storage engine on the 
server.

Before MySQL 5.5, it was MyISAM and after 5.5 it's InnoDB.

Now, though InnoDB is much slower on 5.1 and prior than MyISAM, it's safer to 
use it without the risk of loosing data.
For 5.5 and afterwards, there is no reason to use MyISAM unless you use the 
full text index.

I would like to suggest to force InnoDB or enable the option when installing.
I would, for one, use only InnoDB even with performance hit to know the data is 
safe.

Cheers

Original issue reported on code.google.com by ronen...@gmail.com on 2 May 2012 at 2:03

[GoogleCodeExporter]

I'll see what I can do about this. I guess the options are that

a) new parameter DB_ENGINE that is used just like the table prefix in create 
table scripts

b) use MySQL command "SET storage_engine=XXX;" before running create table 
scripts (but don't know if it works like that, haven't done so)

But since you want to use primarily InnoDB, can't you set is as default?

Original comment by samuli.j...@gmail.com on 6 May 2012 at 3:50

[GoogleCodeExporter]

Hi,

I must state that I'm an employee of Oracle, working in the MySQL team...

Well, the best way to go with it will be to create the table with the statement:
CREATE TABLE ............ ENGINE = 'innodb'

That will make sure you are forcing InnoDB. If, while you're working on the new 
UI you want to allow option (during setup or as part of the settings) to 
choose, that another option.
You can allow to people to move from MyISAM to InnoDB with the ALTER TABLE 
command. As long as you don't have specific need (such as full text index), 
there's no sense to use MyISAM with MySQL 5.5 and up.
On lower versions, it might have some performance issue, but from looking at 
your queries, I don't see big impact.
While InnoDB makes sure that your data is safe. Even if the server crashes.

I changes my tables and it works perfect, at least what I've checked.

And again, thanx for the effort.
I'm trying to get the people that are using your product to donate. You 
definitely worth it!

Original comment by ronen...@gmail.com on 6 May 2012 at 4:41

[GoogleCodeExporter]

Thanks for the info, nice to get feedback from MySQL team :)

Original comment by samuli.j...@gmail.com on 7 May 2012 at 5:42

• Changed state: Accepted

[GoogleCodeExporter]

Added in 1.8.8 (new variable $DB_ENGINE for choosing engine, default "innodb")

Original comment by samuli.j...@gmail.com on 19 May 2012 at 12:04

• Changed state: Fixed

[GoogleCodeExporter]

Great job man!

Original comment by ronen...@gmail.com on 21 May 2012 at 1:36