List:Commits« Previous MessageNext Message »
From:paul.dubois Date:June 8 2010 3:46pm
Subject:svn commit - mysqldoc@docsrva: r21120 - in trunk: . refman-5.0 refman-5.1 refman-5.4 refman-5.5 refman-6.0 refman-common
View as plain text  
Author: paul
Date: 2010-06-08 17:46:38 +0200 (Tue, 08 Jun 2010)
New Revision: 21120

Log:
 r59900@frost:  paul | 2010-06-08 10:32:23 -0500
 Fix docs bug:
 Bug#51058: Recognizing agregated columns in HAVING clausule


Modified:
   trunk/refman-5.0/functions-core.xml
   trunk/refman-5.1/functions-core.xml
   trunk/refman-5.4/functions-core.xml
   trunk/refman-5.5/functions-core.xml
   trunk/refman-6.0/functions-core.xml
   trunk/refman-common/connector-net-visual-studio.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:39186
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:59897
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
   + 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:39186
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:59900
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546


Modified: trunk/refman-5.0/functions-core.xml
===================================================================
--- trunk/refman-5.0/functions-core.xml	2010-06-08 15:37:24 UTC (rev 21119)
+++ trunk/refman-5.0/functions-core.xml	2010-06-08 15:46:38 UTC (rev 21120)
Changed blocks: 1, Lines Added: 32, Lines Deleted: 0; 1512 bytes

@@ -17864,6 +17864,38 @@
       </para>
 
       <para>
+        For example, the following query returns <literal>id</literal>
+        values that occur only once in table <literal>t1</literal>:
+      </para>
+
+<programlisting>
+SELECT id, COUNT(id) FROM t1
+  GROUP BY id
+  HAVING COUNT(id) = 1;
+</programlisting>
+
+      <para>
+        However, the result of the following similar query that uses an
+        alias for the aggregated column depends on the SQL mode:
+      </para>
+
+<programlisting>
+SELECT id, COUNT(id) AS c FROM t1
+  GROUP BY id
+  HAVING c = 1;
+</programlisting>
+
+      <para>
+        In this case, a <literal>non-grouping field 'c' is used in
+        HAVING clause</literal> error occurs if
+        <literal role="sqlmode">ONLY_FULL_GROUP_BY</literal> is enabled
+        because the extension does not apply. The column
+        <literal>c</literal> in the <literal>HAVING</literal> clause is
+        not enclosed in an aggregate function (instead, it
+        <emphasis>is</emphasis> an aggregate function).
+      </para>
+
+      <para>
         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


Modified: trunk/refman-5.1/functions-core.xml
===================================================================
--- trunk/refman-5.1/functions-core.xml	2010-06-08 15:37:24 UTC (rev 21119)
+++ trunk/refman-5.1/functions-core.xml	2010-06-08 15:46:38 UTC (rev 21120)
Changed blocks: 1, Lines Added: 32, Lines Deleted: 0; 1512 bytes

@@ -19311,6 +19311,38 @@
       </para>
 
       <para>
+        For example, the following query returns <literal>id</literal>
+        values that occur only once in table <literal>t1</literal>:
+      </para>
+
+<programlisting>
+SELECT id, COUNT(id) FROM t1
+  GROUP BY id
+  HAVING COUNT(id) = 1;
+</programlisting>
+
+      <para>
+        However, the result of the following similar query that uses an
+        alias for the aggregated column depends on the SQL mode:
+      </para>
+
+<programlisting>
+SELECT id, COUNT(id) AS c FROM t1
+  GROUP BY id
+  HAVING c = 1;
+</programlisting>
+
+      <para>
+        In this case, a <literal>non-grouping field 'c' is used in
+        HAVING clause</literal> error occurs if
+        <literal role="sqlmode">ONLY_FULL_GROUP_BY</literal> is enabled
+        because the extension does not apply. The column
+        <literal>c</literal> in the <literal>HAVING</literal> clause is
+        not enclosed in an aggregate function (instead, it
+        <emphasis>is</emphasis> an aggregate function).
+      </para>
+
+      <para>
         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


Modified: trunk/refman-5.4/functions-core.xml
===================================================================
--- trunk/refman-5.4/functions-core.xml	2010-06-08 15:37:24 UTC (rev 21119)
+++ trunk/refman-5.4/functions-core.xml	2010-06-08 15:46:38 UTC (rev 21120)
Changed blocks: 1, Lines Added: 32, Lines Deleted: 0; 1512 bytes

@@ -19134,6 +19134,38 @@
       </para>
 
       <para>
+        For example, the following query returns <literal>id</literal>
+        values that occur only once in table <literal>t1</literal>:
+      </para>
+
+<programlisting>
+SELECT id, COUNT(id) FROM t1
+  GROUP BY id
+  HAVING COUNT(id) = 1;
+</programlisting>
+
+      <para>
+        However, the result of the following similar query that uses an
+        alias for the aggregated column depends on the SQL mode:
+      </para>
+
+<programlisting>
+SELECT id, COUNT(id) AS c FROM t1
+  GROUP BY id
+  HAVING c = 1;
+</programlisting>
+
+      <para>
+        In this case, a <literal>non-grouping field 'c' is used in
+        HAVING clause</literal> error occurs if
+        <literal role="sqlmode">ONLY_FULL_GROUP_BY</literal> is enabled
+        because the extension does not apply. The column
+        <literal>c</literal> in the <literal>HAVING</literal> clause is
+        not enclosed in an aggregate function (instead, it
+        <emphasis>is</emphasis> an aggregate function).
+      </para>
+
+      <para>
         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


Modified: trunk/refman-5.5/functions-core.xml
===================================================================
--- trunk/refman-5.5/functions-core.xml	2010-06-08 15:37:24 UTC (rev 21119)
+++ trunk/refman-5.5/functions-core.xml	2010-06-08 15:46:38 UTC (rev 21120)
Changed blocks: 1, Lines Added: 32, Lines Deleted: 0; 1512 bytes

@@ -19508,6 +19508,38 @@
       </para>
 
       <para>
+        For example, the following query returns <literal>id</literal>
+        values that occur only once in table <literal>t1</literal>:
+      </para>
+
+<programlisting>
+SELECT id, COUNT(id) FROM t1
+  GROUP BY id
+  HAVING COUNT(id) = 1;
+</programlisting>
+
+      <para>
+        However, the result of the following similar query that uses an
+        alias for the aggregated column depends on the SQL mode:
+      </para>
+
+<programlisting>
+SELECT id, COUNT(id) AS c FROM t1
+  GROUP BY id
+  HAVING c = 1;
+</programlisting>
+
+      <para>
+        In this case, a <literal>non-grouping field 'c' is used in
+        HAVING clause</literal> error occurs if
+        <literal role="sqlmode">ONLY_FULL_GROUP_BY</literal> is enabled
+        because the extension does not apply. The column
+        <literal>c</literal> in the <literal>HAVING</literal> clause is
+        not enclosed in an aggregate function (instead, it
+        <emphasis>is</emphasis> an aggregate function).
+      </para>
+
+      <para>
         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


Modified: trunk/refman-6.0/functions-core.xml
===================================================================
--- trunk/refman-6.0/functions-core.xml	2010-06-08 15:37:24 UTC (rev 21119)
+++ trunk/refman-6.0/functions-core.xml	2010-06-08 15:46:38 UTC (rev 21120)
Changed blocks: 1, Lines Added: 32, Lines Deleted: 0; 1512 bytes

@@ -19837,6 +19837,38 @@
       </para>
 
       <para>
+        For example, the following query returns <literal>id</literal>
+        values that occur only once in table <literal>t1</literal>:
+      </para>
+
+<programlisting>
+SELECT id, COUNT(id) FROM t1
+  GROUP BY id
+  HAVING COUNT(id) = 1;
+</programlisting>
+
+      <para>
+        However, the result of the following similar query that uses an
+        alias for the aggregated column depends on the SQL mode:
+      </para>
+
+<programlisting>
+SELECT id, COUNT(id) AS c FROM t1
+  GROUP BY id
+  HAVING c = 1;
+</programlisting>
+
+      <para>
+        In this case, a <literal>non-grouping field 'c' is used in
+        HAVING clause</literal> error occurs if
+        <literal role="sqlmode">ONLY_FULL_GROUP_BY</literal> is enabled
+        because the extension does not apply. The column
+        <literal>c</literal> in the <literal>HAVING</literal> clause is
+        not enclosed in an aggregate function (instead, it
+        <emphasis>is</emphasis> an aggregate function).
+      </para>
+
+      <para>
         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


Modified: trunk/refman-common/connector-net-visual-studio.xml
===================================================================
--- trunk/refman-common/connector-net-visual-studio.xml	2010-06-08 15:37:24 UTC (rev 21119)
+++ trunk/refman-common/connector-net-visual-studio.xml	2010-06-08 15:46:38 UTC (rev 21120)
Changed blocks: 2, Lines Added: 0, Lines Deleted: 13; 1075 bytes

@@ -1493,13 +1493,6 @@
     </figure>
 
     <para>
-      From the <guilabel>New File</guilabel> dialog select the MySQL
-      template, and then double-click the <guilabel>MySQL SQL
-      Script</guilabel> document, or click the
-      <guibutton>Open</guibutton> button.
-    </para>
-
-    <para>
       The SQL Editor will be displayed. You can now enter SQL code as
       required, or connect to a MySQL server. Click the
       <guibutton>Connect to MySQL</guibutton> button in the SQL Editor

@@ -1526,12 +1519,6 @@
       </mediaobject>
     </figure>
 
-    <para>
-      The results from any queries are displayed on the
-      <guilabel>Results</guilabel> tab. Any errors are displayed on the
-      <guilabel>Messages</guilabel> tab.
-    </para>
-
   </section>
 
 </section>


Thread
svn commit - mysqldoc@docsrva: r21120 - in trunk: . refman-5.0 refman-5.1 refman-5.4 refman-5.5 refman-6.0 refman-commonpaul.dubois8 Jun