bk commit - mysqldoc tree (paul:1.2680)

[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.2680 05/03/08 20:53:07 paul@stripped +1 -0
  manual.texi:
    Document bugfix. (Bug #8218)
    Add section for MyODBC changelog.
    Document bugfix. (Bug #8138)

  Docs/manual.texi
    1.2503 05/03/08 20:49:11 paul@stripped +8 -5

  Docs/manual.texi
    1.2502 05/03/08 20:47:49 paul@stripped +5 -0
    Document bugfix. (Bug #8218)

  Docs/manual.texi
    1.2501 05/03/08 20:40:37 paul@stripped +28 -1
    Add section for MyODBC changelog.
    Document bugfix. (Bug #8138)

# 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.2500/Docs/manual.texi	2005-03-08 17:56:49 -06:00
+++ 1.2503/Docs/manual.texi	2005-03-08 20:49:11 -06:00
@@ -96705,6 +96705,7 @@
 * News-3.19.x::                 Changes in release 3.19.x
 * InnoDB change history::       @code{InnoDB} Change History
 * MySQL Cluster change history::  @code{MySQL Cluster} Change History
+* MyODBC News::                 Changes in MyODBC
 @end menu
 
 
@@ -97010,16 +97011,20 @@
 
 Bugs fixed:
 @itemize @bullet
+@item
+For a query with both @code{GROUP BY} and @code{COUNT(DISTINCT)} clauses and
+a @code{FROM} clause with a subquery, @code{NULL} was returned for any
+@code{VARCHAR} column selected by the subquery.  (Bug #8218)
+@item
 Fixed a bug in @code{TRUNCATE}, which did not work within stored procedures. 
 A workaround has been made so that within stored procedures, @code{TRUNCATE} 
 is executed like @code{DELETE}. This was necessary because @code{TRUNCATE} is 
 implicitly locking tables. (Bug #8850)
 @item
 Fixed an optimizer bug that caused incorrectly ordered result from a query that
-used @code{FULLTEXT} index to retrieve rows and there was another index that
-was usable for @code{ORDER BY}. For such a query @code{EXPLAIN} showed
+used a @code{FULLTEXT} index to retrieve rows and there was another index that
+was usable for @code{ORDER BY}. For such a query, @code{EXPLAIN} showed
 @code{fulltext} join type, but regular (not @code{FULLTEXT}) index in the
-@code{Key} column.  (Bug #6635)
 @item
 If @code{SELECT DISTINCT} named an index column multiple times in the select
 list, the server tried to access different key fields for each instance of the
@@ -97984,9 +97989,13 @@
 Bugs fixed:
 @itemize @bullet
 @item
+For a query with both @code{GROUP BY} and @code{COUNT(DISTINCT)} clauses and
+a @code{FROM} clause with a subquery, @code{NULL} was returned for any
+@code{VARCHAR} column selected by the subquery.  (Bug #8218)
+@item
 Fixed an optimizer bug that caused incorrectly ordered result from a query that
-used @code{FULLTEXT} index to retrieve rows and there was another index that
-was usable for @code{ORDER BY}. For such a query @code{EXPLAIN} showed
+used a @code{FULLTEXT} index to retrieve rows and there was another index that
+was usable for @code{ORDER BY}. For such a query, @code{EXPLAIN} showed
 @code{fulltext} join type, but regular (not @code{FULLTEXT}) index in the
 @code{Key} column.  (Bug #6635)
 @item
@@ -112822,7 +112831,7 @@
 @end itemize
 
 
-@node MySQL Cluster change history,  , InnoDB change history, News
+@node MySQL Cluster change history, MyODBC News, InnoDB change history, News
 @appendixsec @code{MySQL Cluster} Change History
 
 @menu
@@ -113355,6 +113364,32 @@
 @itemize @bullet
 @item
 Various bugs fixed in the development process leading up to 4.1.3.
+@end itemize
+
+
+@node MyODBC News,  , MySQL Cluster change history, News
+@appendixsec Changes in MyODBC
+
+@menu
+* MyODBC News-3.51.11::         Changes in MyODBC 3.51.11
+@end menu
+
+
+@node MyODBC News-3.51.11,  , MyODBC News, MyODBC News
+@appendixsubsec Changes in MyODBC 3.51.11
+
+Functionality added or changed:
+@itemize @bullet
+@item
+@end itemize
+
+Bugs fixed:
+@itemize @bullet
+@item
+@code{SQLGetTypoInfo()} returned @code{tinyblob} for @code{SQL_VARBINARY}
+and nothing for @code{SQL_BINARY}.  Fixed to return @code{varbinary} for
+@code{SQL_VARBINARY}, @code{binary} for @code{SQL_BINARY}, and @code{longblob}
+for @code{SQL_LONGVARBINARY}.
 @end itemize