Bug #32250 references to SQL_MAX_JOIN_SIZE should be replaced with MAX_JOIN_SIZE
Submitted: 9 Nov 2007 21:28 Modified: 9 Jan 2010 23:51
Reporter: Matthew Montgomery Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.0.50 OS:Any
Assigned to: Paul DuBois CPU Architecture:Any

[9 Nov 2007 21:28] Matthew Montgomery
Description:
The variable SQL_MAX_JOIN_SIZE is mentioned on "7.8.5.2. Using the --safe-updates Option" and "5.2.1. Option and Variable Reference"

Since this variable name is being replaced by global and session variable MAX_JOIN_SIZE, the references to the old name should be removed and/or the new variable name should be noted.

How to repeat:
.

Suggested fix:
.
[15 Nov 2007 17:22] 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.

For "7.8.5.2. Using the --safe-updates Option", mysql does in fact send a statement naming SQL_MAX_JOIN_SIZE (not MAX_JOIN_SIZE) to the server. The docs are correct. (It may be that mysql should use the newer variable name, but if so, that is a client bug and not a docs bug until and if that change is made. Please file a separate bug report at your discretion.)

In "5.2.1. Option and Variable Reference", I have made the entry for sql_max_join_size link to the description for max_join_size, where the description mentions that sql_max_join_size is the older name.
[8 Jan 2010 20:41] MySQL Verification Team
This update should extend to the error messages from the server, such as http://dev.mysql.com/doc/refman/5.1/en/error-messages-server.html#error_er_too_big_select
[9 Jan 2010 23:51] Paul DuBois
This is a docs bug report, not a server bug report. Closing this bug again. I've filed Bug#50206 as a followup to address the server error message.