I think Percona with Galera has the option to force all tables to innodb.
I seem to recall that, but it has been months since I touched anything Percona
related. What a blessing that turned out to be.
Sent from my iPhone
> On Dec 22, 2015, at 11:02 AM, Federico Razzoli wrote:
>
> I didn't s
I didn't suggest to use MyISAM :)
Now I understand your purpose. If you use MaxScale, you can use a filter and
replace MyISAM with InnoDB. Something like:
/engine( )*=( *)myisam/i
And you can use similar regexps for each storage engine.
The filter that you need is this one:
https://github.com/ma
Thank you all, we're going to open a bug as soon as possible;
@Federico: Thanks for the suggestion, but we are interested in forcing
engine substitution, because this way a table creation made by a generic
user can be issued using both InnoDB and MyISAM (users can't be always
aware of which en
in my opnion, itś a bug, report to jira issue tracker
2015-12-22 10:00 GMT-02:00 Federico Razzoli :
> Sounds like a bug. But, bug or not bug, I suggest you set sql_mode =
> 'NO_ENGINE_SUBSTITUTION'. Changes to non-InnoDB tables are NOT replicated.
> (There seems to be a sort of support for MyISAM
Sounds like a bug. But, bug or not bug, I suggest you set sql_mode =
'NO_ENGINE_SUBSTITUTION'. Changes to non-InnoDB tables are NOT replicated.
(There seems to be a sort of support for MyISAM, but it's unreliable and needs
to be manually enabled on all nodes)
Federico
Thanks guys,
as Ian has pointed out, in recent releases sql_mode contains by default
NO_ENGINE_SUBSTITUTION so in our deployment we set sql_mode to blank to
gracefully use InnoDB when MyISAM table creation is issued.
To be clearer on the problem we're experiencing, I'll paste some console
outpu
6 matches
Mail list logo
