[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mysql-internals
Subject:    bk commit - mysqldoc@docsrva tree (paul:1.2732)
From:       paul () mysql ! com
Date:       2005-05-31 16:08:41
Message-ID: 20050531160841.5F72D2812D9 () frost ! snake ! net
[Download RAW message or body]

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.2732 05/05/31 11:08:32 paul@frost.snake.net +1 -0
  manual.texi:
    Correct error in description of OPTIONALLY for
    FIELDS ENCLOSED BY.
    Fix a couple of changelog entries.

  Docs/manual.texi
    1.2957 05/05/31 11:07:56 paul@frost.snake.net +2 -1
    Correct error in description of OPTIONALLY for
    FIELDS ENCLOSED BY.

  Docs/manual.texi
    1.2956 05/05/31 10:55:20 paul@frost.snake.net +9 -8
    Fix a couple of changelog entries.

# 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.2955/Docs/manual.texi	2005-05-31 07:20:49 -05:00
+++ 1.2957/Docs/manual.texi	2005-05-31 11:07:56 -05:00
@@ -56166,7 +56166,8 @@
 @end example
 
 If you specify @code{OPTIONALLY}, the @code{ENCLOSED BY} character is
-used only to enclose @code{CHAR} and @code{VARCHAR} fields:
+used only to enclose values in columns that have a string data type (such
+as @code{CHAR}, @code{BINARY}, @code{TEXT}, or @code{ENUM}):
 
 @example
 1,"a string",100.20
@@ -100331,11 +100332,6 @@
 Functionality added or changed:
 @itemize @bullet
 @item
-Multiple table @code{DELETE} did always delete on the fly from the
-first table that was to be deleted from.  In some cases when using
-many tables and with a need to access the same row twice in the first table
-we could miss some rows-to-be-deleted from other tables. This is now fixed.
-@item
 @code{SHOW BINARY LOGS} now displays a @code{File_size} column that indicates
 the size of each file.
 @item
@@ -100360,8 +100356,14 @@
 Bugs fixed:
 @itemize @bullet
 @item
-The @code{mysql_next_result()} function could hang if one of the statements
-executed was illegal.  (Bug #9992)
+Multiple-table @code{DELETE} did always delete on the fly from the first
+table that was to be deleted from.  In some cases, when using many tables
+and it was necessary to access the same row twice in the first table, we
+could miss some rows-to-be-deleted from other tables. This is now fixed.
+@item
+The @code{mysql_next_result()} function could hang if you were executing many
+statements in a @code{mysql_real_query()} call and one of those statements
+raised an error.  (Bug #9992)
 @item
 The combination of @code{COUNT()}, @code{DISTINCT}, and @code{CONCAT()}
 sometimes triggered a memory deallocation bug on Windows resulting in a
@@ -102342,7 +102344,7 @@
 Locking for @code{CREATE TABLE ... SELECT} for @code{InnoDB} tables was
 too weak.  It allowed @code{INSERT} statements issued for the created table
 while the @code{CREATE TABLE} statement was still running to appear in the
-binary log to appear before the @code{CREATE TABLE} statement.  (Bug #6678)
+binary log before the @code{CREATE TABLE} statement.  (Bug #6678)
 @item
 @code{InnoDB}: In @code{DROP DATABASE}, check for all referencing tables
 from other databases before dropping any tables.  (Bug #10335)

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

[prev in list] [next in list] [prev in thread] [next in thread]