Bug #31454 mysqldump --compatible=no_field_options does not remove field options

• Submitted: 8 Oct 2007 15:16
• Modified: 7 Jun 2009 19:33
• Reporter: Tobias Schwinger
• Status: No Feedback
• Category: MySQL Server: mysqldump Command-line Client
• Severity: S3 (Non-critical)
• Version: 4.1.2, 5.0
• OS: Any
• CPU Architecture: Any

[8 Oct 2007 15:16] Tobias Schwinger

Description:

$ mysqldump --compatible=no_field_options ...

Produces output that still contains field options.

How to repeat:
Given a MySql server that hosts databases with field options, the output of

$ mysqldump --compatible=no_field_options --all-databases

will contain field options.

Suggested fix:
$ mysqldump --compatbile=mysql40 ...

Can serve as a workaround, as it causes field options to be omitted (also changes operator precedence, though).

[8 Oct 2007 18:41] MySQL Verification Team

Thank you for the bug report.

[7 May 2009 19:33] Jim Winstead

There are only a few possible field properties that NO_FIELD_OPTIONS controls (in 5.0): "AUTO_INCREMENT", "USING <algorithm>", and "on update CURRENT_TIMESTAMP".

I don't see any problem with these, but there's not enough information in this bug report to know what field options you are still seeing reported.

[7 Jun 2009 23:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".