MySQL Bugs: #7699: documentation 4.0 cannot replicate 4.1

Bug #7699	documentation 4.0 cannot replicate 4.1
Submitted:	6 Jan 2005 11:26	Modified:	3 Feb 2005 17:28
Reporter:	Martin Friebe (Gold Quality Contributor) (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:		OS:
Assigned to:	Paul DuBois	CPU Architecture:	Any

Description:
http://dev.mysql.com/doc/mysql/en/Replication_Compatibility.html

the documentation states a slave of "mysql 4.0.3 and up" would be able to   be a slave to any master mysql 4.0 and 4.1.
this is not entirely correct, see the sql statement in how to repeat.

it works on mysql 4.1, but it will stop any 4.0 slave

"6.7 Replication Features and Known Problems" contains some warnings about character set, but I havent found anything about the usage f "gorup_concat" or similiar.

How to repeat:
#set up 4.1.x master
#set up 4.0.x slave

#run on master

create table x1 select * from x2 order by x2.c1 collate latin1_bin;

# will also happen with any other new feature, like group_concat

Suggested fix:
since 4.1.7 has several new features,, that can not be replicatabled by 4.0; please change the documentation to indicate this

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
product(s).

Additional info:

The referenced section pertains to replication protocol
compatibility, but the COLLATE and GROUP_CONCAT()
issues pertain to SQL compatibility.  They're specific
instances of a more general constraint on replicating new
features to old servers. I'm adding a note about this
to the "Replication Features" section.

http://dev.mysql.com/doc/mysql/en/replication-features.html

Thanks for the report.