Bug #31619 rpl_innodb_mixed_dml fails, unordered select

• Submitted: 15 Oct 2007 21:51
• Modified: 28 Feb 2008 19:11
• Reporter: Timothy Smith
• Status: Closed
• Category: Tests: Replication
• Severity: S3 (Non-critical)
• Version: 5.1, 5.2
• OS: Any
• Assigned to: Serge Kozlov
• CPU Architecture: Any
• Tags: pbfail

[15 Oct 2007 21:51] Timothy Smith

Description:
rpl.rpl_innodb_mixed_dml       [ fail ]

--- C:/cygwin/home/pushbuild/pb1/pb/mysql-6.0-falcon/11/mysql-6.0.4-alpha-pb11/mysql-test/suite/rpl/r/rpl_innodb_mixed_dml.result	2007-10-03 08:32:34.000000000 +0300
+++ e:\var-n_mix-100\log\rpl_innodb_mixed_dml.reject	2007-10-03 10:36:36.000000000 +0300
@@ -198,8 +198,8 @@
 2	DDD	2	CCC
 SELECT * FROM t1 INNER JOIN  t2 ON t1.b = t2.b;
 a	b	a	b
-1	CCC	2	CCC
 2	DDD	1	DDD
+1	CCC	2	CCC
 DELETE FROM t1;
 DELETE FROM t2;
 

mysqltest: Result content mismatch

How to repeat:
https://intranet.mysql.com/secure/pushbuild/xref.pl?testname=rpl.rpl_innodb_mixed_dml

Suggested fix:
Add an ORDER BY clause on the select in question.

[16 Oct 2007 17:35] Matthias Leich

What about inserting 
"--sorted_result"
just before the SELECT giving the unstable result ?
Advantage: No change of the SELECT, no impact on optimizer ...

[26 Nov 2007 15:37] Serge Kozlov

The test case was already fixed for mysql-5.1-new-rpl

[28 Feb 2008 19:11] Serge Kozlov

fixed