maria-discuss team mailing list archive

[Peter Laursen <peter_laursen@xxxxxxxxxx>]

At least the error/warning message is wrong IMO.

>> this
Table storage engine 'InnoDB' does not support the create option
'TRANSACTIONAL=1'
>> should rather be something like
Table storage engine 'InnoDB' does not support the create option
'TRANSACTIONAL'. We preserve it though so that ALTER operation can reversed"

In Haralds test case it was 'TRANSACTIONAL=0'. But it does not matter if it
was "1" or 0". The same error or warning occurs.

And if it confuses clients, applications and scripts (as Harald reports
with phpMyAdmin), how do we remove it? Is there an ALTER TABLE statement
that can do it (like "ALTER TABLE .. CLEANUP CREATE_OPTIONS;" removing any
option that has no effect with current storage engine)?


-- Peter

On Mon, Mar 2, 2015 at 3:03 PM, Ian Gilfillan <ian@xxxxxxxxxxx> wrote:

>
> 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.
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~maria-discuss
> Post to     : maria-discuss@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maria-discuss
> More help   : https://help.launchpad.net/ListHelp
>