Bug #36341 ndb_update_no_read fails with embedded + cluster
Submitted: 25 Apr 2008 13:55 Modified: 3 Apr 2014 8:57
Reporter: Magnus Blåudd Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-6.3 OS:Any
Assigned to: Magnus Blåudd CPU Architecture:Any

[25 Apr 2008 13:55] Magnus Blåudd
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 Blåudd
Similar to BUG#33036
[8 May 2008 8:38] Jonas Oreland
also ndb_sql_allow_batching
[3 Apr 2014 8:57] Magnus Blåudd
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html