Bug #36341 ndb_update_no_read fails with embedded + cluster
Submitted: 25 Apr 2008 13:55
Reporter: Magnus Blaudd Email Updates:
Status: Verified
Category:Server: Cluster Severity:S3 (Non-critical)
Version:mysql-5.1-telco-6.3 OS:Any
Assigned to: Magnus Blaudd Target Version:CGE-6.3
Triage: Triaged: D3 (Medium)

[25 Apr 2008 13:55] Magnus Blaudd 
Description:

ndb.ndb_update_no_read         [ fail ]

---
/data0/pushbuild/pb2/pb/mysql-5.1-telco-6.3/289/mysql-5.1.24-ndb-6.3.13-pb289/mysql-test/suite/ndb/r/ndb_update_no_read.result	2008-04-24
14:29:31.000000000 +0300
+++
/data0/pushbuild/pb2/pb/mysql-5.1-telco-6.3/289/mysql-5.1.24-ndb-6.3.13-pb289/mysql-test/suite/ndb/r/ndb_update_no_read.reject	2008-04-24
17:45:52.366841405 +0300
@@ -17,7 +17,7 @@
 affected rows: 1
 info: Rows matched: 1  Changed: 1  Warnings: 0
 @ndb_execute_count:=VARIABLE_VALUE-@ndb_init_execute_count
-2
+3
 affected rows: 1
 select * from t1 where a = 1 order by a;
 a	b	c

The first testcase in the file  fails with an extra roundtrip to the server. Most likely
the "info call".

How to repeat:
mysql-5.1-telco-6.3$>./mtr --embedded
[25 Apr 2008 13:56] Magnus Blaudd 
Similar to BUG#33036
[8 May 2008 8:38] Jonas Oreland 
also ndb_sql_allow_batching