Bug #66639 Please keep client side of mysql-cluster and mysql in source code sync
Submitted: 31 Aug 2012 22:34
Reporter: Nicholas Bamber (OCA) Email Updates:
Status: Open Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S4 (Feature request)
Version:any OS:Any
Assigned to: CPU Architecture:Any

[31 Aug 2012 22:34] Nicholas Bamber
This is a request from a Debian MySQL maintainer about how the MySQL and MySQL cluster code bases should be managed. I understand that they are separate products   developed by separate teams and that they cannot be expected to release comparable versions necessarily in sync. 

However on the client side, the libraries, the mysql binary etc (essentially anything that connects to the server over a TCP connection in a standardized manner) should not diverge between the two products over time. I am aware of two cases where this seems to be happening:

1.) The bind-address option is explicitly supported in the MySQL cluster version only. (note that the feature is documented in the core code so this cannot really be a delay in synchronization). 
2.) The copyright statements are out of sync (though I could accept that this is just a delay in synchronization). 

How to repeat:
Diffing the code. 

Suggested fix:
I would like a commitment that the two teams will work to keep the client sides of the code source identical over time by means of regular mergings.