bk commit - mysqldoc tree (marko:1.2651)

[Marko Mäkelä]

Below is the list of changes that have just been committed into a local
mysqldoc repository of marko. When marko 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.2651 05/03/07 10:12:06 marko@stripped +1 -0
  manual.texi:
    News-4.1.11, News-5.0.3: Document the recent change in OPTIMIZE TABLE.
    InnoDB will commit it every 10,000 copied rows,
    just like ALTER TABLE, CREATE INDEX and DROP INDEX.

  Docs/manual.texi
    1.2471 05/03/07 10:10:42 marko@stripped +6 -5
    News-4.1.11, News-5.0.3: Document the recent change in OPTIMIZE TABLE.
    InnoDB will commit it every 10,000 copied rows,
    just like ALTER TABLE, CREATE INDEX and DROP INDEX.

# 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:	marko
# Host:	hundin.mysql.fi
# Root:	/home/marko/k/mysqldoc

--- 1.2470/Docs/manual.texi	Mon Mar  7 03:39:11 2005
+++ 1.2471/Docs/manual.texi	Mon Mar  7 10:10:42 2005
@@ -96664,8 +96664,9 @@
 for compatibility with MySQL 4.1. (Bug #7856)
 @item
 @code{InnoDB}: Commit after every 10,000 copied rows when executing
-@code{ALTER TABLE}, @code{CREATE INDEX} or @code{DROP INDEX}.  This makes it
-much faster to recover from an aborted operation.
+@code{ALTER TABLE}, @code{CREATE INDEX}, @code{DROP INDEX} or
+@code{OPTIMIZE TABLE}.  This makes it much faster to recover from an
+aborted operation.
 @item
 Added @code{VAR_POP()} and @code{STDDEV_POP()} as standard SQL aliases for
 the @code{VARIANCE()} and @code{STDDEV()} functions that compute population
@@ -97756,9 +97757,9 @@
 not to be recorded. (Bug #6662)
 @item
 @code{InnoDB}: Commit after every 10,000 copied rows when executing
-@code{CREATE INDEX} or @code{DROP INDEX}, which are internally implemented
-as @code{ALTER TABLE}.  This makes it much faster to recover from an
-aborted operation.
+@code{CREATE INDEX}, @code{DROP INDEX} or @code{OPTIMIZE TABLE}, which
+are internally implemented as @code{ALTER TABLE}.  This makes it much
+faster to recover from an aborted operation.
 @end itemize
 
 Bugs fixed: