Bug #70281 sql_safe_updates documentation needs improvement
Submitted: 9 Sep 2013 21:40 Modified: 26 Sep 2013 17:34
Reporter: monty solomon Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.5.31 OS:Any
Assigned to: Paul DuBois CPU Architecture:Any

[9 Sep 2013 21:40] monty solomon 
Description:
Please change

If set to 1, MySQL aborts UPDATE or DELETE statements that do not use a key in the WHERE clause or a LIMIT clause.

to

If set to 1, MySQL aborts UPDATE or DELETE statements that do not use a key in the WHERE clause or do not use a LIMIT clause.

How to repeat:
https://dev.mysql.com/doc/refman/5.5/en/server-system-variables.html#sysvar_sql_safe_updat...

Suggested fix:
Please change

If set to 1, MySQL aborts UPDATE or DELETE statements that do not use a key in the WHERE clause or a LIMIT clause.

to

If set to 1, MySQL aborts UPDATE or DELETE statements that do not use a key in the WHERE clause or do not use a LIMIT clause.
[11 Sep 2013 10:50] MySQL Verification Team 
Hello monty,

Thank you for the report.

Thanks,
Umesh
[26 Sep 2013 17:34] 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.

Revised text:

If set to 1, MySQL aborts UPDATE or DELETE statements that do not use
a key in the WHERE clause or a LIMIT clause. (Specifically, UPDATE
statements must have a WHERE clause that uses a key or a LIMIT
clause, or both. DELETE statements must have both.) This makes it 
possible to catch UPDATE or DELETE statements where keys are not used
properly and that would probably change or delete a large number of
rows. The default value is 0.