MySQL Bugs: #9394: mysqldump --compatible=... not matching with expectations

Bug #9394	mysqldump --compatible=... not matching with expectations
Submitted:	24 Mar 2005 22:27	Modified:	9 Sep 2005 19:20
Reporter:	Hartmut Holzgraefe	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:		OS:
Assigned to:	Bugs System	CPU Architecture:	Any

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
The manual description of mysqldump option --compatible 
doesn't make it clear enough that this option does not yet
provide *full* compatibility with other databases other than
older MySQL releases.

It only sets those sql_mode options that are currently 
available to the right values needed for the requested database
but does not provide mapping of data types or e.g. Oracles
different COMMENT syntax.

How to repeat:
mysqldump --compatible=oracle ....

Datatypes will not be Oracle types but still MySQL ones 
(e.g. no VARCHAR -> VARCHAR2 conversion)

Suggested fix:
Add a warning to the documentation of this option 
to prevent false expectations

Documentation issue.