2 Mar
2015
2 Mar
'15
3:03 p.m.
On 02/03/2015 15:37, Reindl Harald wrote:
Am 02.03.2015 um 14:26 schrieb Ian Gilfillan:
This is probably because strict mode is set. If unset, it should return a warning, not an error. From MariaDB 10.1.2, you can use: SET STATEMENT sql_mode='' FOR ALTER TABLE `systemevents` ENGINE = InnoDB; which will unset strict mode just for that query, otherwise for older versions just set it off and on again for the session to alter.
indeed *but* why does "TRANSACTIONAL=0" don't go away after convert to InnoDB?
Why is so that the change is reversible. Obviously this may not be desirable in many cases. See https://mariadb.atlassian.net/browse/MDEV-5867 for a similar discussion and a fix that was applied in 10.0.13.