bk commit - mysqldoc tree (paul:1.2868)

[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.2868 05/04/14 18:18:26 paul@stripped +2 -0
  Further clarification of ORDER BY w/LIMIT.

  Docs/manual.texi
    1.2700 05/04/14 18:18:21 paul@stripped +7 -5
    Further clarification of ORDER BY w/LIMIT.

  Docs/internals.texi
    1.73 05/04/14 18:14:34 paul@stripped +1 -1
    Further clarification of ORDER BY w/LIMIT.

# 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:	frost.snake.net
# Root:	/Volumes/frost2/MySQL/bk/mysqldoc

--- 1.2699/Docs/manual.texi	2005-04-14 15:46:03 -05:00
+++ 1.2700/Docs/manual.texi	2005-04-14 18:18:21 -05:00
@@ -35554,11 +35554,13 @@
 @item
 If you use @code{LIMIT @var{row_count}} with @code{ORDER BY}, MySQL ends the
 sorting as soon as it has found the first @var{row_count} rows of the sorted
-result, rather than sorting the entire result.  If ordering is done by using an
-index, this is very fast.  If a filesort must be done, more work is necessary
-before it can be ascertained that the first @var{row_count} rows have been
-found.  In either case, once the rows have been found, there is no need to
-sort any remainder of the result set, and MySQL does not do so.
+result, rather than sorting the entire result.  If ordering is done by using
+an index, this is very fast.  If a filesort must be done, all rows that
+match the query without the @code{LIMIT} clause must be selected, and most
+or all of them must be sorted, before it can be ascertained that the first
+@var{row_count} rows have been found.  In either case, once the rows have
+been found, there is no need to sort any remainder of the result set, and
+MySQL does not do so.
 @item
 When combining @code{LIMIT @var{row_count}} with @code{DISTINCT}, MySQL stops
 as soon as it finds @var{row_count} unique rows.

--- 1.72/Docs/internals.texi	2005-03-23 13:45:03 -06:00
+++ 1.73/Docs/internals.texi	2005-04-14 18:14:34 -05:00
@@ -21,7 +21,7 @@
 
 @c Set background for HTML
 @set _body_tags BGCOLOR=#FFFFFF TEXT=#000000 LINK=#101090 VLINK=#7030B0
-@settitle MySQL Internals Manual for version @value{mysqlversion}.
+@settitle MySQL Internals Manual
 @setchapternewpage odd
 @paragraphindent 0