bk commit - mysqldoc tree (1.456)

Below is the list of changes that have just been committed into a local
mysqldoc repository of monty. When monty 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.456 03/04/28 10:48:37 monty@xxxxxxxxxxxxxxx +1 -0
  Updated information for FOUND_ROWS()

  Docs/manual.texi
    1.430 03/04/28 10:48:36 monty@xxxxxxxxxxxxxxx +6 -2
    Updated information for FOUND_ROWS()

# 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: monty
# Host: mashka.mysql.fi
# Root: /home/my/mysqldoc

--- 1.429/Docs/manual.texi      Sun Apr 27 22:03:28 2003
+++ 1.430/Docs/manual.texi      Mon Apr 28 10:48:36 2003
@@ -36096,8 +36096,9 @@
 @findex FOUND_ROWS()
 @findex LIMIT
 @item FOUND_ROWS()
-Returns the number of rows that the last @code{SELECT SQL_CALC_FOUND_ROWS ...}
-command would have returned, if it had not been restricted with @code{LIMIT}.
+Returns the number of rows that the preceding @code{SELECT
+SQL_CALC_FOUND_ROWS ...} command would have returned, if it had not been
+restricted with @code{LIMIT}.
 
 @example
 mysql> SELECT SQL_CALC_FOUND_ROWS * FROM tbl_name
@@ -36113,6 +36114,9 @@
 to calculate all rows in the result set.  However, this is faster than
 if you would not use @code{LIMIT}, as the result set need not be sent
 to the client.
+
+The value of @code{FOUND_ROWS()} is only relevant directly after a
+@code{SELECT SQL_CALC_FOUND_ROWS} command.
 
 @code{SQL_CALC_FOUND_ROWS} is available starting at MySQL version 4.0.0.
 @end table

-- 
MySQL Internals Mailing List
For list archives: http://lists.mysql.com/internals
To unsubscribe:    
http://lists.mysql.com/internals?unsub=gcdmd-internals@xxxxxxxxxxx