Make InnoDB the default MySql engine for table creation about squeryl

[dflemstr]

Why? Shouldn't this be done with the MySQL administration tools? It's not the task of Squeryl to manage database-specific defaults, I think.

But as you said on the mailing list: if a solution is found for setting engines per-table, it'd be the way to go.

[max-l]

I think I see you point, but I thought that having MyISAM as the default adapter sucks, since it misleads those who think they are getting transactional behavior, don't you think ?

[dflemstr]

Yes, it sucks, but it would be better in that case to disable the transaction functionality in Squeryl completely (e.g. by raising an exception if the engine doesn't support transactions, so that the dev is inclined to switch engine) when MyISAM is active, instead of ignoring the problem and going with a different engine. That's at least what I think.

Many (most?) MySQL installations use InnoDB per default, so this is only an issue for a few people.

[max-l]

I can imagine some cases where people will use InnoDB for most of there application, (to get transactionality) but use MyISAM for a few tables, where they want maximum read performance. I've read about such uses cases where one has an application database on InnoDB, and a data warehouse on MyISAM.

[max-l]

Perhaps a solution can be to simply have a constructor param in the MySQLAdapter that is the engine name, this has the advantage of forcing the user to make a concious choice, or at least to inform the user that such a choice exists.

[nairbv]

Actually, it uses MyISAM by default:

mysql> create table foo(id int);
Query OK, 0 rows affected (0.01 sec)

mysql> show create table foo;
+-------+-----------------------------------------------------------------------------------------+
| Table | Create Table |
+-------+-----------------------------------------------------------------------------------------+
| foo | CREATE TABLE foo (
id int(11) default NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1 |
+-------+-----------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

It's a bit odd, but, that's how they get their fancy benchmarks.

I would certainly prefer if MySQL used InnoDB as a default, but it would be unexpected behaviour for that choice to be made in a client-side library.

I like the idea of throwing an exception if a user tries to start a transaction on a MyISAM table.

[max-l]

closed since :
b701a9e