Bug #54215 | Example SET scope defaults to GLOBAL, should specify SESSION | ||
---|---|---|---|
Submitted: | 3 Jun 2010 18:23 | Modified: | 9 Jun 2010 1:33 |
Reporter: | Ronald Bradford | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.1.39 | OS: | MacOS (N/A) |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
Tags: | document, set scope |
[3 Jun 2010 18:23]
Ronald Bradford
[4 Jun 2010 2:36]
Paul DuBois
There is no GLOBAL autocommit prior to 5.5.3. Presumably what you are seeing is that SHOW GLOBAL VARIABLES shows the session value if there is no global value. From 5.5.3 on, you will observe different behavior, I believe, because there is a GLOBAL autocommit.
[9 Jun 2010 1:33]
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. Updated text: With the GLOBAL modifier, SHOW VARIABLES displays the values that are used for new connections to MySQL. As of MySQL 5.5.3, if a variable has no global value, no value is displayed. Before 5.5.3, the session value is displayed. With SESSION, SHOW VARIABLES displays the values that are in effect for the current connection. If no modifier is present, the default is SESSION. LOCAL is a synonym for SESSION.