Bug #69142 FAQ about SQL Mode is outdated
Submitted: 3 May 2013 23:38 Modified: 24 Feb 2015 14:21
Reporter: Jaime Crespo (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.6,5.7 OS:Any
Assigned to: Paul DuBois CPU Architecture:Any
Tags: doc, documentation, faq, mode, SQL, SQL_MODE

[3 May 2013 23:38] Jaime Crespo
Description:
SQL Modes FAQ Still mention old defaults. 

How to repeat:
Go to:
http://dev.mysql.com/doc/refman/5.6/en/faqs-sql-modes.html
http://dev.mysql.com/doc/refman/5.7/en/faqs-sql-modes.html

Section:
B.3.7: What is the default server SQL mode when My SQL 5.X is installed?

Where it says:

By default, no special modes are enabled.

Suggested fix:
It should say:

The default SQL mode is NO_ENGINE_SUBSTITUTION; in MySQL 5.6.5 and earlier, it was empty.

(or something similar).
[4 May 2013 0:46] MySQL Verification Team
Thank you for the bug report.
[5 Jun 2013 17:53] Paul DuBois
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 products.
[23 Feb 2015 12:08] Jaime Crespo
A typo was introduced when rewriting my suggestion, it now says:

"As of MySQL 5.6.6, the default SQL mode is NO_ENGINE_SUBSTITUTION. Before 5.6.6, the default mode was empty (no modes enabled). it was empty."

5.7 version should be also updated (I can open other bug if necessary):

Instead of:

"The default SQL mode is NO_ENGINE_SUBSTITUTION."

It should say:

"The default SQL mode in MySQL 5.7 is ONLY_FULL_GROUP_BY,NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES (NO_ENGINE_SUBSTITUTION before MySQL 5.7.5)."

Sorry again to report such a tiny problems. Maybe you'd prefer to delete the entire FAQ question and redirect to the main entry to avoid further problems.
[24 Feb 2015 14:21] Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly.

Let's see if I got it right this time. :-)