bk commit - mysqldoc tree (paul:1.2774)

[paul]

Below is the list of changes that have just been committed into a local
mysqldoc repository of paul. When paul does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html

ChangeSet
  1.2774 05/03/24 11:48:20 paul@stripped +1 -0
  manual.texi:
    Constrain the conclusions that may be drawn from a failed
    mysql_ping() call.

  Docs/manual.texi
    1.2608 05/03/24 11:47:33 paul@stripped +5 -3
    Constrain the conclusions that may be drawn from a failed
    mysql_ping() call.

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	paul
# Host:	kite-hub.kitebird.com
# Root:	/src/extern/MySQL/bk/mysqldoc

--- 1.2607/Docs/manual.texi	2005-03-24 11:41:31 -06:00
+++ 1.2608/Docs/manual.texi	2005-03-24 11:47:33 -06:00
@@ -84360,8 +84360,8 @@
 
 @subsubheading Description
 
-Checks whether the connection to the server is working. If it has gone
-down, an automatic reconnection is attempted.
+Checks whether the connection to the server is working. If the connection
+has gone down, an automatic reconnection is attempted.
 
 This function can be used by clients that remain idle for a long while,
 to check whether the server has closed the connection and reconnect
@@ -84369,7 +84369,9 @@
 
 @subsubheading Return Values
 
-Zero if the server is alive. Non-zero if an error occurred.
+Zero if the connection to the server is alive. Non-zero if an error occurred.
+A non-zero return does not indicate whether the MySQL server itself is down;
+the connection might be broken for other reasons such as network problems.
 
 @subsubheading Errors