Bug #8901 mysqldump needs mysql41 compatibility mode
Submitted: 2 Mar 2005 19:44 Modified: 9 Oct 2005 23:16
Reporter: Paul DuBois Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: mysqldump Command-line Client Severity:S4 (Feature request)
Version:MySQL 5 OS:Any
Assigned to: CPU Architecture:Any

[2 Mar 2005 19:44] Paul DuBois
mysqldump supports a --compatible option so that
you can dump tables in a way that will be compatible
with older MySQL servers (or other database servers).
The set of MySQL compatiblity modes are mysql323 and
mysql40. Now that we have MySQL 5.0, we need a mysql41
compatability mode to account for things that are true
in 5.0 but not in 4.1.  For example, if you dump a FEDERATED
table or a VARCHAR(>255), the table structures won't be
loadable into a 4.1 server without some modification.

How to repeat:
Dump a table with a VARCHAR(256) column and try to
load it into MySQL 4.1.
[2 Mar 2005 19:45] Paul DuBois
Changing to feature request.
[3 Apr 2007 16:53] Paul DuBois
Now that we have MySQL 5.1, we could also
use a mysql50 compatibility mode.
[16 Apr 2008 16:19] Paul DuBois
Bug#25162 illustrates one reason why we need --compatible=mysql50.
[16 Apr 2008 16:20] Paul DuBois
Now that we have MySQL 6.0, we could also
use a mysql51 compatibility mode.