| Bug #3532 | Documentation thinko | ||
|---|---|---|---|
| Submitted: | 22 Apr 2004 1:37 | Modified: | 22 Apr 2004 4:51 |
| Reporter: | Matthias Urlichs | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
| Version: | current | OS: | - |
| Assigned to: | CPU Architecture: | Any | |
[22 Apr 2004 4:51]
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 product(s). Additional info: Thanks for spotting this. Actually, the same problem occurred later in the paragraph as well.

Description: From mysqldoc/Doc/manual.texi: rather than just the @code{SESSION} variable for its own connection. If we add a @code{SESSION} variable with the same name as a @code{SESSION} variable, a client that intends to change the @code{GLOBAL} variable might find only its own @code{SESSION} variable changed. In the second line, the second SESSION needs to be replaced with GLOBAL. How to repeat: - Suggested fix: The fix may be pulled from bk://smurf.bkbits.net/tmp/mysqldoc