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

[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.2750 05/06/10 13:26:55 paul@stripped +1 -0
  manual.texi:
    Document bugfix. (Bug #10975)
    Document bugfix. (Bug #7115)
    Document bugfix. (Bug #10605)
    Document bugfix. (Bug #11088)
    Document bugfix. (Bug #11153)
    Document bugfix. (Bug #10729)

  Docs/manual.texi
    1.2966 05/06/10 13:25:04 paul@stripped +20 -0
    Document bugfix. (Bug #10975)
    Document bugfix. (Bug #7115)
    Document bugfix. (Bug #10605)

  Docs/manual.texi
    1.2965 05/06/10 13:08:08 paul@stripped +8 -0
    Document bugfix. (Bug #11088)

  Docs/manual.texi
    1.2964 05/06/10 13:03:05 paul@stripped +3 -0
    Document bugfix. (Bug #11153)

  Docs/manual.texi
    1.2963 05/06/10 12:59:28 paul@stripped +4 -0
    Document bugfix. (Bug #10729)

# 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.2962/Docs/manual.texi	2005-06-10 12:55:54 -05:00
+++ 1.2966/Docs/manual.texi	2005-06-10 13:25:04 -05:00
@@ -64765,6 +64765,10 @@
 @code{mysql_stmt_prepare()} C API function to prepare a @code{PREPARE},
 @code{EXECUTE}, or @code{DEALLOCATE PREPARE} statement.
 
+@c Restriction implemented in 5.0.8; may be lifted later
+SQL syntax for prepared statements cannot be used within stored procedures
+and functions.
+
 
 
 @node Storage engines, InnoDB, SQL Syntax, Top
@@ -80097,6 +80101,8 @@
 
 @c TODO: note restricted statements.
 @c FLUSH disallowed in stored functions.
+@c Dynamic SQL (PREPARE, EXECUTE, DEALLOCATE) disallowed in stored routines
+@c (see Bug #10975, Bug #7115, Bug #10605)
 
 @cindex stored procedures
 @cindex procedures, stored
@@ -100363,6 +100369,24 @@
 
 Bugs fixed:
 @itemize @bullet
+@item
+Using @code{PREPARE} to prepare a statement that invoked a stored routine that
+deallocated the prepared statement caused a server crash.  This is prevented
+by disabling dynamic SQL within stored routines.  (Bug #10975)
+@item
+Using @code{PREPARE} to prepare a statement that invoked a stored routine
+that executed the prepared statement caused a @code{Packets out of order}
+error the second time the routine was invoked.  This is prevented by
+disabling dynamic SQL within stored routines.  (Bug #7115)
+@item
+Using prepared statements within a stored routine (@code{PREPARE},
+@code{EXECUTE}, @code{DEALLOCATE}) could cause the client connection to
+be dropped after the routine returned.  This is prevented by disabling
+dynamic SQL within stored routines.  (Bug #10605)
+@item
+When using a cursor with a prepared statement, the first execution returned
+the correct result but was not cleaned up properly, causing subsequent
+executions to return incorrect results.  (Bug #10729)
 @end itemize
 
 @node News-5.0.7, News-5.0.6, News-5.0.8, News-5.0.x
@@ -100399,6 +100423,13 @@
 Bugs fixed:
 @itemize @bullet
 @item
+Fixed a server crash resulting from an attempt to allocate too much memory
+when @code{GROUP BY @var{blob_col}} and @code{COUNT(DISTINCT)} were used.
+(Bug #11088)
+@item
+Fixed a portability problem for compiling on Windows with Visual Studio 6.
+(Bug #11153)
+@item
 The incorrect sequence of statements @code{HANDLER @var{tbl_name} READ
 @var{index_name} NEXT} without a preceding @code{HANDLER @var{tbl_name} READ
 @var{index_name} = (@var{value_list})} for an @code{InnoDB} table resulted
@@ -102465,6 +102496,10 @@
 
 Bugs fixed:
 @itemize @bullet
+@item
+Fixed a server crash resulting from an attempt to allocate too much memory
+when @code{GROUP BY @var{blob_col}} and @code{COUNT(DISTINCT)} were used.
+(Bug #11088)
 @item
 The incorrect sequence of statements @code{HANDLER @var{tbl_name} READ
 @var{index_name} NEXT} without a preceding @code{HANDLER @var{tbl_name} READ