[MDEV-6988] Inconsistent warning, only with CONNECT Created: 2014-10-31  Updated: 2014-11-01  Resolved: 2014-11-01

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - Connect
Affects Version/s: 10.0.14
Fix Version/s: 10.0.15

Type: Bug Priority: Minor
Reporter: Federico Razzoli Assignee: Olivier Bertrand
Resolution: Fixed Votes: 0
Labels: connect-engine


 Description    

MariaDB [xxx]> LOCK TABLE m WRITE;
 
Query OK, 0 rows affected (0.00 sec)
 
 
 
MariaDB [xxx]> START TRANSACTION;
 
Query OK, 0 rows affected (0.00 sec)
 
 
 
MariaDB [xxx]> LOCK TABLE t WRITE;
 
Query OK, 0 rows affected (0.00 sec)
 
 
 
MariaDB [xxx]> START TRANSACTION;
 
Query OK, 0 rows affected, 1 warning (0.00 sec)
 
 
 
Warning (Code 1105): external_lock: unexpected command 59

The table `m` is MyISAM but, as far as I can tell, no warning occurs with other storage engines. The table `t` is CONNECT, which seems to be the only engine that issues a warning.

I report this behavior because you probably want to be aware about inconsistencies between engines. But, to be honest, I prefer CONNECT's behavior: when a trx starts, table locks are lost, and this is something I want to know. I hope that a more informative warning will be issued, no matter which engine I am using.

 Comments   
Comment by Elena Stepanova [ 2014-11-01 ]

Hi Federico,

Thanks. Inconsistency is always suspicious, e.g. as soon as I started verifying it, I got this: MDEV-6994.

And of course if the warning happens to be intentional, it should come with a better message.

Comment by Olivier Bertrand [ 2014-11-01 ]

I can easily suppress this warning. Changing it for a more informative warning should done only according to what other engines do.

Comment by Olivier Bertrand [ 2014-11-01 ]

Warning suppressed

Generated at Thu Feb 08 07:16:06 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.