Bug #117618 Erroneous warning "Combining the storage engines InnoDB and MyISAM is deprecated"

• Submitted: 4 Mar 14:31
• Modified: 5 Mar 6:13
• Reporter: Kamil Holubicki (OCA)
• Status: Verified
• Category: MySQL Server: Replication
• Severity: S3 (Non-critical)
• Version: 9.1, 9.2.0
• OS: Any
• CPU Architecture: Any
• Tags: Contribution, regression

[4 Mar 14:31] Kamil Holubicki

Description:
| Warning | 6414 | Combining the storage engines InnoDB and MyISAM is deprecated, but the statement or transaction updates both the InnoDB table test.t2_innodb and the MyISAM table test.t1_myisam. |

is reported, but it should not be.

It is caused by commit 9e1c2f9e

How to repeat:
create database test;
use test;
create table t1_myisam(a int) engine=myisam;
create table t2_innodb(a int) engine=innodb;
set session sql_log_bin=0;
insert into t1_myisam values (0);
set session sql_log_bin=1;
insert into t2_innodb values (0);
Query OK, 1 row affected, 1 warning (0,00 sec)

mysql> show warnings;
+---------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Level   | Code | Message                                                                                                                                                                           |
+---------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Warning | 6414 | Combining the storage engines InnoDB and MyISAM is deprecated, but the statement or transaction updates both the InnoDB table test.t2_innodb and the MyISAM table test.t1_myisam. |
+---------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0,00 sec)

[4 Mar 14:32] Kamil Holubicki

proposed patch

(*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: 9e1c2f9e.patch (text/x-patch), 1.39 KiB.

[4 Mar 14:33] Kamil Holubicki

I think it can be solved in a better way than in a submitted patch, but I think it shows what is happening.

[5 Mar 6:13] MySQL Verification Team

Hello Kamil Holubicki ,

Thank you for the report and contribution.

regards,
Umesh