bk commit - mysqldoc@docsrva tree (paul:1.2785)

[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.2785 05/06/14 21:43:31 paul@stripped +3 -0
  Move a script.

  DocsX/Makefile
    1.71 05/06/14 21:43:23 paul@stripped +3 -1
    Move a script.

  tools/chapterfmt.pl
    1.5 05/06/14 21:41:06 paul@stripped +0 -0
    Rename: DocsX/chapterfmt.pl -> tools/chapterfmt.pl

  Docs/manual.texi
    1.3001 05/06/14 14:42:14 paul@stripped +13 -13
    Move two changelog entries from 5.0.5 to 5.0.6.

# 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.3000/Docs/manual.texi	2005-06-14 14:26:54 -05:00
+++ 1.3001/Docs/manual.texi	2005-06-14 14:42:14 -05:00
@@ -100935,6 +100935,19 @@
 Bugs fixed:
 @itemize @bullet
 @item
+Statements that create and use stored routines were not being written to the
+binary log, which affects replication and data recovery options.
+(Bug #2610)
+@c TODO: uncomment the following after adding the xref-ed section
+@c Stored routine-related statements now are logged, subject to the
+@c issues and limitations discussed in [ADD XREF].
+@item
+Disabled binary logging within stored routines to avoid writing spurious
+extra statements to the binary log.  For example, if a routine @code{p()}
+executes an @code{INSERT} statement, then for @code{CALL p()}, the
+@code{CALL} statement appears in the binary log, but not the @code{INSERT}
+statement.  (Bug #9100)
+@item
 Statements that create and drop triggers were not being written to the
 binary log, which affects replication and data recovery options.
 (Bug #10417)
@@ -101163,19 +101176,6 @@
 @code{--user=@var{non_existent_user}}, it would run using the privileges of the
 account it was invoked from, even if that was @code{root}.  (Bug #9833)
 
-@item
-Statements that create and use stored routines were not being written to the
-binary log, which affects replication and data recovery options.
-(Bug #2610)
-@c TODO: uncomment the following after adding the xref-ed section
-@c Stored routine-related statements now are logged, subject to the
-@c issues and limitations discussed in [ADD XREF].
-@item
-Disabled binary logging within stored routines to avoid writing spurious
-extra statements to the binary log.  For example, if a routine @code{p()}
-executes an @code{INSERT} statement, then for @code{CALL p()}, the
-@code{CALL} statement appears in the binary log, but not the @code{INSERT}
-statement.  (Bug #9100)
 @item
 Corrected a failure to resolve a column reference correctly for a @code{LEFT
 JOIN} that compared a join column to an @code{IN} subquery.  (Bug #9338)

--- 1.70/DocsX/Makefile	2005-06-10 15:26:29 -05:00
+++ 1.71/DocsX/Makefile	2005-06-14 21:43:23 -05:00
@@ -534,8 +534,10 @@
 		"Installing MySQL on NetWare" \
 		> $@
 
+CHAPTERFMT = $(TOOLS_DIR)/chapterfmt.pl
+
 ReadMe.html: manual.xml
-	./chapterfmt.pl --no-rebuild mac-os-x-installation.html
+	$(CHAPTERFMT) --no-rebuild mac-os-x-installation.html
 	mv mac-os-x-installation.html ReadMe.html
 	$(RM) mac-os-x-installation.*