MySQL Bugs: #68810: description error in DOC5.6 16.4.1.8.1 replication with more columns on....

Bug #68810	description error in DOC5.6 16.4.1.8.1 replication with more columns on....
Submitted:	29 Mar 2013 1:40	Modified:	25 Jun 2013 11:24
Reporter:	h h	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.6	OS:	Any
Assigned to:	Jon Stephens	CPU Architecture:	Any

Description:
here is the text in mysql5.6 document about replication

Columns common to both versions of the table must be defined before any additional columns.

This means that executing an ALTER TABLE statement on the slave where a new column is inserted into the table within the range of columns common to both tables causes replication to fail, as shown in the following example:

Suppose that a table t, existing on the master and the slave, is defined by the following CREATE TABLE statement:

CREATE TABLE t (
    c1 INT,
    c2 INT,
    c3 INT
); 
Suppose that the ALTER TABLE statement shown here is executed on the slave:

ALTER TABLE t ADD COLUMN cnew1 INT AFTER c3;
The previous ALTER TABLE is permitted on the slave because the columns c1, c2, and c3 that are common to both versions of table t remain grouped together in both versions of the table, before any columns that differ.

However, the following ALTER TABLE statement cannot be executed on the slave without causing replication to break:

ALTER TABLE t ADD COLUMN cnew2 INT AFTER c3;
Replication fails after execution on the slave of the ALTER TABLE statement just shown, because the new column cnew2 comes between columns common to both versions of t.

i think the second statement is error 
ALTER TABLE t ADD COLUMN cnew2 INT AFTER c3;

the correct statement is 
ALTER TABLE t ADD COLUMN cnew2 INT AFTER c2;

How to repeat:
see mysql5.6 document 
16.4.1.8.1 replication with more columns on master or slave

Corrected documentation (*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: replication.patch (text/x-patch), 931 bytes.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.