List:Commits« Previous MessageNext Message »
From:paul.dubois Date:May 3 2011 10:44pm
Subject:svn commit - mysqldoc@oter02: r26119 - in trunk: . refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0
View as plain text  
Author: pd221994
Date: 2011-05-04 00:44:06 +0200 (Wed, 04 May 2011)
New Revision: 26119

Log:
 r47692@dhcp-adc-twvpn-1-vpnpool-10-154-23-122:  paul | 2011-05-03 17:38:16 -0500
 Update GROUP BY/ONLY_FULL_GROUP_BY description


Modified:
   svk:merge
   trunk/refman-5.0/functions-core.xml
   trunk/refman-5.1/functions-core.xml
   trunk/refman-5.5/functions-core.xml
   trunk/refman-5.6/functions-core.xml
   trunk/refman-6.0/functions-core.xml

Property changes on: trunk
___________________________________________________________________

Modified: svk:merge
===================================================================


Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 1277 bytes


Modified: trunk/refman-5.0/functions-core.xml
===================================================================
--- trunk/refman-5.0/functions-core.xml	2011-05-03 22:43:50 UTC (rev 26118)
+++ trunk/refman-5.0/functions-core.xml	2011-05-03 22:44:06 UTC (rev 26119)
Changed blocks: 6, Lines Added: 23, Lines Deleted: 29; 4690 bytes

@@ -18500,9 +18500,8 @@
         BY</literal> clause cannot refer to nonaggregated columns in the
         select list that are not named in the <literal>GROUP
         BY</literal> clause. For example, this query is illegal in
-        standard SQL because the select list refers to the
-        <literal>name</literal> column, which is not named in the
-        <literal>GROUP BY</literal>:
+        standard SQL because the <literal>name</literal> column in the
+        select list does not appear in the <literal>GROUP BY</literal>:
       </para>
 
 <programlisting>

@@ -18513,7 +18512,7 @@
 </programlisting>
 
       <para>
-        For the query to be legal, the query would have to omit the
+        For the query to be legal, it must omit the
         <literal>name</literal> column from the select list or name it
         in the <literal>GROUP BY</literal> clause.
       </para>

@@ -18524,22 +18523,15 @@
         named in the <literal>GROUP BY</literal> clause. This means that
         the preceding query is legal in MySQL. You can use this feature
         to get better performance by avoiding unnecessary column sorting
-        and grouping.
-      </para>
-
-      <para>
-        However, this feature is useful primarily when all values in
-        each nonaggregated column not named in the <literal>GROUP
-        BY</literal> are the same for each group. The server is free to
-        return any value from each group, so unless they are the same,
-        the values chosen are indeterminate.
-      </para>
-
-      <para>
-        The selection of values from each group cannot be influencedby
-        adding an <literal>ORDER BY</literal> clause. Sorting of the
-        result set occurs after values have been chosen, and
-        <literal>ORDER BY</literal> does not affect which values the
+        and grouping. However, this feature is useful primarily when all
+        values in each nonaggregated column not named in the
+        <literal>GROUP BY</literal> are the same for each group. The
+        server is free to return any value from each group, so unless
+        they are the same, the values chosen are indeterminate.
+        Furthermore, the selection of values from each group cannot be
+        influenced by adding an <literal>ORDER BY</literal> clause.
+        Sorting of the result set occurs after values have been chosen,
+        and <literal>ORDER BY</literal> does not affect which values the
         server chooses.
       </para>
 

@@ -18560,10 +18552,7 @@
         BY</literal> does not apply. That is, columns not named in the
         <literal>GROUP BY</literal> clause cannot be used in the select
         list or <literal>HAVING</literal> clause if not enclosed in an
-        aggregate function. However, as mentioned previously,
-        <literal>ORDER BY</literal> does not affect which values are
-        chosen from nonaggregated columns; it only sorts them after they
-        have been chosen.
+        aggregate function.
       </para>
 
       <para>

@@ -18602,8 +18591,11 @@
         The select list extension also applies to <literal>ORDER
         BY</literal>. That is, you can use nonaggregated columns or
         calculations in the <literal>ORDER BY</literal> clause that do
-        not appear in the <literal>GROUP BY</literal> clause. This
-        extension does not apply if the
+        not appear in the <literal>GROUP BY</literal> clause. (However,
+        as mentioned previously, <literal>ORDER BY</literal> does not
+        affect which values are chosen from nonaggregated columns; it
+        only sorts them after they have been chosen.) This extension
+        does not apply if the
         <literal role="sqlmode">ONLY_FULL_GROUP_BY</literal> SQL mode is
         enabled.
       </para>

@@ -18611,9 +18603,11 @@
       <para>
         In some cases, you can use <literal role="func">MIN()</literal>
         and <literal role="func">MAX()</literal> to obtain a specific
-        column value even if it is not unique. The following gives the
-        value of <literal>column</literal> from the row containing the
-        smallest value in the <literal>sort</literal> column:
+        column value even if it is not unique. If the
+        <literal>sort</literal> column contains integers no larger than
+        6 digits, the following query gives the value of
+        <literal>column</literal> from the row containing the smallest
+        <literal>sort</literal> value:
       </para>
 
 <programlisting>


Modified: trunk/refman-5.1/functions-core.xml
===================================================================
--- trunk/refman-5.1/functions-core.xml	2011-05-03 22:43:50 UTC (rev 26118)
+++ trunk/refman-5.1/functions-core.xml	2011-05-03 22:44:06 UTC (rev 26119)
Changed blocks: 6, Lines Added: 23, Lines Deleted: 29; 4690 bytes

@@ -20030,9 +20030,8 @@
         BY</literal> clause cannot refer to nonaggregated columns in the
         select list that are not named in the <literal>GROUP
         BY</literal> clause. For example, this query is illegal in
-        standard SQL because the select list refers to the
-        <literal>name</literal> column, which is not named in the
-        <literal>GROUP BY</literal>:
+        standard SQL because the <literal>name</literal> column in the
+        select list does not appear in the <literal>GROUP BY</literal>:
       </para>
 
 <programlisting>

@@ -20043,7 +20042,7 @@
 </programlisting>
 
       <para>
-        For the query to be legal, the query would have to omit the
+        For the query to be legal, it must omit the
         <literal>name</literal> column from the select list or name it
         in the <literal>GROUP BY</literal> clause.
       </para>

@@ -20054,22 +20053,15 @@
         named in the <literal>GROUP BY</literal> clause. This means that
         the preceding query is legal in MySQL. You can use this feature
         to get better performance by avoiding unnecessary column sorting
-        and grouping.
-      </para>
-
-      <para>
-        However, this feature is useful primarily when all values in
-        each nonaggregated column not named in the <literal>GROUP
-        BY</literal> are the same for each group. The server is free to
-        return any value from each group, so unless they are the same,
-        the values chosen are indeterminate.
-      </para>
-
-      <para>
-        The selection of values from each group cannot be influencedby
-        adding an <literal>ORDER BY</literal> clause. Sorting of the
-        result set occurs after values have been chosen, and
-        <literal>ORDER BY</literal> does not affect which values the
+        and grouping. However, this feature is useful primarily when all
+        values in each nonaggregated column not named in the
+        <literal>GROUP BY</literal> are the same for each group. The
+        server is free to return any value from each group, so unless
+        they are the same, the values chosen are indeterminate.
+        Furthermore, the selection of values from each group cannot be
+        influenced by adding an <literal>ORDER BY</literal> clause.
+        Sorting of the result set occurs after values have been chosen,
+        and <literal>ORDER BY</literal> does not affect which values the
         server chooses.
       </para>
 

@@ -20090,10 +20082,7 @@
         BY</literal> does not apply. That is, columns not named in the
         <literal>GROUP BY</literal> clause cannot be used in the select
         list or <literal>HAVING</literal> clause if not enclosed in an
-        aggregate function. However, as mentioned previously,
-        <literal>ORDER BY</literal> does not affect which values are
-        chosen from nonaggregated columns; it only sorts them after they
-        have been chosen.
+        aggregate function.
       </para>
 
       <para>

@@ -20132,8 +20121,11 @@
         The select list extension also applies to <literal>ORDER
         BY</literal>. That is, you can use nonaggregated columns or
         calculations in the <literal>ORDER BY</literal> clause that do
-        not appear in the <literal>GROUP BY</literal> clause. This
-        extension does not apply if the
+        not appear in the <literal>GROUP BY</literal> clause. (However,
+        as mentioned previously, <literal>ORDER BY</literal> does not
+        affect which values are chosen from nonaggregated columns; it
+        only sorts them after they have been chosen.) This extension
+        does not apply if the
         <literal role="sqlmode">ONLY_FULL_GROUP_BY</literal> SQL mode is
         enabled.
       </para>

@@ -20141,9 +20133,11 @@
       <para>
         In some cases, you can use <literal role="func">MIN()</literal>
         and <literal role="func">MAX()</literal> to obtain a specific
-        column value even if it is not unique. The following gives the
-        value of <literal>column</literal> from the row containing the
-        smallest value in the <literal>sort</literal> column:
+        column value even if it is not unique. If the
+        <literal>sort</literal> column contains integers no larger than
+        6 digits, the following query gives the value of
+        <literal>column</literal> from the row containing the smallest
+        <literal>sort</literal> value:
       </para>
 
 <programlisting>


Modified: trunk/refman-5.5/functions-core.xml
===================================================================
--- trunk/refman-5.5/functions-core.xml	2011-05-03 22:43:50 UTC (rev 26118)
+++ trunk/refman-5.5/functions-core.xml	2011-05-03 22:44:06 UTC (rev 26119)
Changed blocks: 6, Lines Added: 23, Lines Deleted: 29; 4690 bytes

@@ -20341,9 +20341,8 @@
         BY</literal> clause cannot refer to nonaggregated columns in the
         select list that are not named in the <literal>GROUP
         BY</literal> clause. For example, this query is illegal in
-        standard SQL because the select list refers to the
-        <literal>name</literal> column, which is not named in the
-        <literal>GROUP BY</literal>:
+        standard SQL because the <literal>name</literal> column in the
+        select list does not appear in the <literal>GROUP BY</literal>:
       </para>
 
 <programlisting>

@@ -20354,7 +20353,7 @@
 </programlisting>
 
       <para>
-        For the query to be legal, the query would have to omit the
+        For the query to be legal, it must omit the
         <literal>name</literal> column from the select list or name it
         in the <literal>GROUP BY</literal> clause.
       </para>

@@ -20365,22 +20364,15 @@
         named in the <literal>GROUP BY</literal> clause. This means that
         the preceding query is legal in MySQL. You can use this feature
         to get better performance by avoiding unnecessary column sorting
-        and grouping.
-      </para>
-
-      <para>
-        However, this feature is useful primarily when all values in
-        each nonaggregated column not named in the <literal>GROUP
-        BY</literal> are the same for each group. The server is free to
-        return any value from each group, so unless they are the same,
-        the values chosen are indeterminate.
-      </para>
-
-      <para>
-        The selection of values from each group cannot be influencedby
-        adding an <literal>ORDER BY</literal> clause. Sorting of the
-        result set occurs after values have been chosen, and
-        <literal>ORDER BY</literal> does not affect which values the
+        and grouping. However, this feature is useful primarily when all
+        values in each nonaggregated column not named in the
+        <literal>GROUP BY</literal> are the same for each group. The
+        server is free to return any value from each group, so unless
+        they are the same, the values chosen are indeterminate.
+        Furthermore, the selection of values from each group cannot be
+        influenced by adding an <literal>ORDER BY</literal> clause.
+        Sorting of the result set occurs after values have been chosen,
+        and <literal>ORDER BY</literal> does not affect which values the
         server chooses.
       </para>
 

@@ -20401,10 +20393,7 @@
         BY</literal> does not apply. That is, columns not named in the
         <literal>GROUP BY</literal> clause cannot be used in the select
         list or <literal>HAVING</literal> clause if not enclosed in an
-        aggregate function. However, as mentioned previously,
-        <literal>ORDER BY</literal> does not affect which values are
-        chosen from nonaggregated columns; it only sorts them after they
-        have been chosen.
+        aggregate function.
       </para>
 
       <para>

@@ -20443,8 +20432,11 @@
         The select list extension also applies to <literal>ORDER
         BY</literal>. That is, you can use nonaggregated columns or
         calculations in the <literal>ORDER BY</literal> clause that do
-        not appear in the <literal>GROUP BY</literal> clause. This
-        extension does not apply if the
+        not appear in the <literal>GROUP BY</literal> clause. (However,
+        as mentioned previously, <literal>ORDER BY</literal> does not
+        affect which values are chosen from nonaggregated columns; it
+        only sorts them after they have been chosen.) This extension
+        does not apply if the
         <literal role="sqlmode">ONLY_FULL_GROUP_BY</literal> SQL mode is
         enabled.
       </para>

@@ -20452,9 +20444,11 @@
       <para>
         In some cases, you can use <literal role="func">MIN()</literal>
         and <literal role="func">MAX()</literal> to obtain a specific
-        column value even if it is not unique. The following gives the
-        value of <literal>column</literal> from the row containing the
-        smallest value in the <literal>sort</literal> column:
+        column value even if it is not unique. If the
+        <literal>sort</literal> column contains integers no larger than
+        6 digits, the following query gives the value of
+        <literal>column</literal> from the row containing the smallest
+        <literal>sort</literal> value:
       </para>
 
 <programlisting>


Modified: trunk/refman-5.6/functions-core.xml
===================================================================
--- trunk/refman-5.6/functions-core.xml	2011-05-03 22:43:50 UTC (rev 26118)
+++ trunk/refman-5.6/functions-core.xml	2011-05-03 22:44:06 UTC (rev 26119)
Changed blocks: 6, Lines Added: 23, Lines Deleted: 29; 4690 bytes

@@ -20690,9 +20690,8 @@
         BY</literal> clause cannot refer to nonaggregated columns in the
         select list that are not named in the <literal>GROUP
         BY</literal> clause. For example, this query is illegal in
-        standard SQL because the select list refers to the
-        <literal>name</literal> column, which is not named in the
-        <literal>GROUP BY</literal>:
+        standard SQL because the <literal>name</literal> column in the
+        select list does not appear in the <literal>GROUP BY</literal>:
       </para>
 
 <programlisting>

@@ -20703,7 +20702,7 @@
 </programlisting>
 
       <para>
-        For the query to be legal, the query would have to omit the
+        For the query to be legal, it must omit the
         <literal>name</literal> column from the select list or name it
         in the <literal>GROUP BY</literal> clause.
       </para>

@@ -20714,22 +20713,15 @@
         named in the <literal>GROUP BY</literal> clause. This means that
         the preceding query is legal in MySQL. You can use this feature
         to get better performance by avoiding unnecessary column sorting
-        and grouping.
-      </para>
-
-      <para>
-        However, this feature is useful primarily when all values in
-        each nonaggregated column not named in the <literal>GROUP
-        BY</literal> are the same for each group. The server is free to
-        return any value from each group, so unless they are the same,
-        the values chosen are indeterminate.
-      </para>
-
-      <para>
-        The selection of values from each group cannot be influencedby
-        adding an <literal>ORDER BY</literal> clause. Sorting of the
-        result set occurs after values have been chosen, and
-        <literal>ORDER BY</literal> does not affect which values the
+        and grouping. However, this feature is useful primarily when all
+        values in each nonaggregated column not named in the
+        <literal>GROUP BY</literal> are the same for each group. The
+        server is free to return any value from each group, so unless
+        they are the same, the values chosen are indeterminate.
+        Furthermore, the selection of values from each group cannot be
+        influenced by adding an <literal>ORDER BY</literal> clause.
+        Sorting of the result set occurs after values have been chosen,
+        and <literal>ORDER BY</literal> does not affect which values the
         server chooses.
       </para>
 

@@ -20750,10 +20742,7 @@
         BY</literal> does not apply. That is, columns not named in the
         <literal>GROUP BY</literal> clause cannot be used in the select
         list or <literal>HAVING</literal> clause if not enclosed in an
-        aggregate function. However, as mentioned previously,
-        <literal>ORDER BY</literal> does not affect which values are
-        chosen from nonaggregated columns; it only sorts them after they
-        have been chosen.
+        aggregate function.
       </para>
 
       <para>

@@ -20792,8 +20781,11 @@
         The select list extension also applies to <literal>ORDER
         BY</literal>. That is, you can use nonaggregated columns or
         calculations in the <literal>ORDER BY</literal> clause that do
-        not appear in the <literal>GROUP BY</literal> clause. This
-        extension does not apply if the
+        not appear in the <literal>GROUP BY</literal> clause. (However,
+        as mentioned previously, <literal>ORDER BY</literal> does not
+        affect which values are chosen from nonaggregated columns; it
+        only sorts them after they have been chosen.) This extension
+        does not apply if the
         <literal role="sqlmode">ONLY_FULL_GROUP_BY</literal> SQL mode is
         enabled.
       </para>

@@ -20801,9 +20793,11 @@
       <para>
         In some cases, you can use <literal role="func">MIN()</literal>
         and <literal role="func">MAX()</literal> to obtain a specific
-        column value even if it is not unique. The following gives the
-        value of <literal>column</literal> from the row containing the
-        smallest value in the <literal>sort</literal> column:
+        column value even if it is not unique. If the
+        <literal>sort</literal> column contains integers no larger than
+        6 digits, the following query gives the value of
+        <literal>column</literal> from the row containing the smallest
+        <literal>sort</literal> value:
       </para>
 
 <programlisting>


Modified: trunk/refman-6.0/functions-core.xml
===================================================================
--- trunk/refman-6.0/functions-core.xml	2011-05-03 22:43:50 UTC (rev 26118)
+++ trunk/refman-6.0/functions-core.xml	2011-05-03 22:44:06 UTC (rev 26119)
Changed blocks: 6, Lines Added: 23, Lines Deleted: 29; 4690 bytes

@@ -20632,9 +20632,8 @@
         BY</literal> clause cannot refer to nonaggregated columns in the
         select list that are not named in the <literal>GROUP
         BY</literal> clause. For example, this query is illegal in
-        standard SQL because the select list refers to the
-        <literal>name</literal> column, which is not named in the
-        <literal>GROUP BY</literal>:
+        standard SQL because the <literal>name</literal> column in the
+        select list does not appear in the <literal>GROUP BY</literal>:
       </para>
 
 <programlisting>

@@ -20645,7 +20644,7 @@
 </programlisting>
 
       <para>
-        For the query to be legal, the query would have to omit the
+        For the query to be legal, it must omit the
         <literal>name</literal> column from the select list or name it
         in the <literal>GROUP BY</literal> clause.
       </para>

@@ -20656,22 +20655,15 @@
         named in the <literal>GROUP BY</literal> clause. This means that
         the preceding query is legal in MySQL. You can use this feature
         to get better performance by avoiding unnecessary column sorting
-        and grouping.
-      </para>
-
-      <para>
-        However, this feature is useful primarily when all values in
-        each nonaggregated column not named in the <literal>GROUP
-        BY</literal> are the same for each group. The server is free to
-        return any value from each group, so unless they are the same,
-        the values chosen are indeterminate.
-      </para>
-
-      <para>
-        The selection of values from each group cannot be influencedby
-        adding an <literal>ORDER BY</literal> clause. Sorting of the
-        result set occurs after values have been chosen, and
-        <literal>ORDER BY</literal> does not affect which values the
+        and grouping. However, this feature is useful primarily when all
+        values in each nonaggregated column not named in the
+        <literal>GROUP BY</literal> are the same for each group. The
+        server is free to return any value from each group, so unless
+        they are the same, the values chosen are indeterminate.
+        Furthermore, the selection of values from each group cannot be
+        influenced by adding an <literal>ORDER BY</literal> clause.
+        Sorting of the result set occurs after values have been chosen,
+        and <literal>ORDER BY</literal> does not affect which values the
         server chooses.
       </para>
 

@@ -20692,10 +20684,7 @@
         BY</literal> does not apply. That is, columns not named in the
         <literal>GROUP BY</literal> clause cannot be used in the select
         list or <literal>HAVING</literal> clause if not enclosed in an
-        aggregate function. However, as mentioned previously,
-        <literal>ORDER BY</literal> does not affect which values are
-        chosen from nonaggregated columns; it only sorts them after they
-        have been chosen.
+        aggregate function.
       </para>
 
       <para>

@@ -20734,8 +20723,11 @@
         The select list extension also applies to <literal>ORDER
         BY</literal>. That is, you can use nonaggregated columns or
         calculations in the <literal>ORDER BY</literal> clause that do
-        not appear in the <literal>GROUP BY</literal> clause. This
-        extension does not apply if the
+        not appear in the <literal>GROUP BY</literal> clause. (However,
+        as mentioned previously, <literal>ORDER BY</literal> does not
+        affect which values are chosen from nonaggregated columns; it
+        only sorts them after they have been chosen.) This extension
+        does not apply if the
         <literal role="sqlmode">ONLY_FULL_GROUP_BY</literal> SQL mode is
         enabled.
       </para>

@@ -20743,9 +20735,11 @@
       <para>
         In some cases, you can use <literal role="func">MIN()</literal>
         and <literal role="func">MAX()</literal> to obtain a specific
-        column value even if it is not unique. The following gives the
-        value of <literal>column</literal> from the row containing the
-        smallest value in the <literal>sort</literal> column:
+        column value even if it is not unique. If the
+        <literal>sort</literal> column contains integers no larger than
+        6 digits, the following query gives the value of
+        <literal>column</literal> from the row containing the smallest
+        <literal>sort</literal> value:
       </para>
 
 <programlisting>


Thread
svn commit - mysqldoc@oter02: r26119 - in trunk: . refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0paul.dubois4 May