bk commit - mysqldoc tree (paul:1.2732)

[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.2732 05/03/15 15:00:01 paul@stripped +1 -0
  manual.texi:
    Document {SUM,MIN,MAX,AVG}(DISTINCT).

  Docs/manual.texi
    1.2562 05/03/15 14:59:39 paul@stripped +26 -9
    Document {SUM,MIN,MAX,AVG}(DISTINCT).

# 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:	kite-hub.kitebird.com
# Root:	/src/extern/MySQL/bk/mysqldoc

--- 1.2561/Docs/manual.texi	2005-03-15 14:31:47 -06:00
+++ 1.2562/Docs/manual.texi	2005-03-15 14:59:39 -06:00
@@ -53102,10 +53102,14 @@
 
 @table @code
 
-@c description_for_help_topic AVG
+@c description_for_help_topic AVG  DISTINCT
 @findex AVG()
-@item AVG(@var{expr})
+@findex AVG(DISTINCT)
+@findex DISTINCT
+@item AVG([DISTINCT] @var{expr})
 Returns the average value of @code{@var{expr}}.
+The @code{DISTINCT} option can be used as of MySQL 5.0.3 to return the averge
+of the distinct values of @var{expr}.
 @c end_description_for_help_topic
 
 @c example_for_help_topic AVG
@@ -53274,14 +53278,20 @@
 to using @code{DISTINCT} together with @code{ORDER BY}. To work around
 this limitation, use @code{MID(@var{expr},1,255)} instead.
 
-@c description_for_help_topic MIN MAX  MIN MAX
+@c description_for_help_topic MIN MAX  MIN MAX DISTINCT
 @findex MIN()
+@findex MIN(DISTINCT)
 @findex MAX()
-@item MIN(@var{expr})
-@itemx MAX(@var{expr})
+@findex MAX(DISTINCT)
+@findex DISTINCT
+@item MIN([DISTINCT] @var{expr})
+@itemx MAX([DISTINCT] @var{expr})
 Returns the minimum or maximum value of @var{expr}.  @code{MIN()} and
 @code{MAX()} may take a string argument; in such cases they return the
 minimum or maximum string value. @xref{MySQL indexes}.
+The @code{DISTINCT} keyword can be used as of MySQL 5.0.0 to find the minimum
+or maximum of the distinct values of @var{expr}; this is supported, but
+produces the same result as omitting @code{DISTINCT}.
 @c end_description_for_help_topic
 
 @c example_for_help_topic MIN MAX
@@ -53326,11 +53336,15 @@
 @code{VAR_SAMP()}.  This function was added in MySQL 5.0.3.
 @c end_description_for_help_topic
 
-@c description_for_help_topic SUM
+@c description_for_help_topic SUM  DISTINCT
 @findex SUM()
-@item SUM(@var{expr})
+@findex SUM(DISTINCT)
+@findex DISTINCT
+@item SUM([DISTINCT] @var{expr})
 Returns the sum of @var{expr}.  If the return set has no rows,
 @code{SUM()} returns @code{NULL}.
+The @code{DISTINCT} keyword can be used as of MySQL 5.0.0 to sum only the
+distinct values of @var{expr}.
 @c end_description_for_help_topic
 
 @c description_for_help_topic VAR_POP
@@ -96731,8 +96745,6 @@
 @item
 Add all missing standard SQL and ODBC 3.0 types.
 @item
-Add @code{SUM(DISTINCT)}.
-@item
 @code{INSERT SQL_CONCURRENT} and @command{mysqld --concurrent-insert} to do
 a concurrent insert at the end of a table if the table is read-locked.
 @item
@@ -97149,6 +97161,8 @@
 (Thanks to Stefano Di Paola @email{stefano.dipaola@@wisec.it} for finding
 and informing us about this issue.)
 @item
+Added support for @code{AVG(DISTINCT)}.
+@item
 @code{ONLY_FULL_GROUP_BY} no longer is included in the @code{ANSI} composite
 SQL mode.  (Bug #8510)
 @item
@@ -98218,6 +98232,9 @@
 
 Functionality added or changed:
 @itemize @bullet
+@item
+Added support for @code{SUM(DISTINCT)}, @code{MIN(DISTINCT)}, and
+@code{MAX(DISTINCT)}.
 @item
 The @code{KILL} statement now takes @code{CONNECTION} and @code{QUERY}
 modifiers. The first is the same as @code{KILL} with no modifier (it