MySQL Bugs: #34860: --compat for non-mysql servers should also enable --skip-opt for compatibility

Bug #34860	--compat for non-mysql servers should also enable --skip-opt for compatibility
Submitted:	26 Feb 2008 20:37	Modified:	26 Feb 2008 21:41
Reporter:	Tobias Asplund	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Command-line Clients	Severity:	S4 (Feature request)
Version:	5.1.23	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
mysqldump has the option to make output compatible to import into other RDBMSs.

The problem here is that the --opt flag that is enabled by default since 4.1 actually uses multi-line inserts that aren't compatible with some of them.

How to repeat:
mysqldump --compat=mssql

Suggested fix:
We could probably fix this by using --skip-opt for compat modes with databases that doesn't support that syntax.

Thank you for the report.

According to http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html#option_mysqldump_compatible: "This option does not guarantee compatibility with other servers. It only enables those SQL mode values that are currently available for making dump output more compatible." and http://dev.mysql.com/doc/refman/5.1/en/server-sql-mode.html: "MSSQL Equivalent to PIPES_AS_CONCAT, ANSI_QUOTES, IGNORE_SPACE, NO_KEY_OPTIONS, NO_TABLE_OPTIONS, NO_FIELD_OPTIONS." this is not a bug. So I reclassified report to feature request.