List:Commits« Previous MessageNext Message »
From:paul.dubois Date:March 14 2011 3:25pm
Subject:svn commit - mysqldoc@oter02: r25372 - 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-03-14 16:25:47 +0100 (Mon, 14 Mar 2011)
New Revision: 25372

Log:
 r45860@dhcp-adc-twvpn-1-vpnpool-10-154-16-169:  paul | 2011-03-14 09:11:04 -0500
 Reorder paras, add note about unparenthesized UNION


Modified:
   svk:merge
   trunk/refman-5.0/sql-syntax-data-manipulation.xml
   trunk/refman-5.1/sql-syntax-data-manipulation.xml
   trunk/refman-5.5/sql-syntax-data-manipulation.xml
   trunk/refman-5.6/sql-syntax-data-manipulation.xml
   trunk/refman-6.0/sql-syntax-data-manipulation.xml

Property changes on: trunk
___________________________________________________________________

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


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


Modified: trunk/refman-5.0/sql-syntax-data-manipulation.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-data-manipulation.xml	2011-03-14 15:03:40 UTC (rev 25371)
+++ trunk/refman-5.0/sql-syntax-data-manipulation.xml	2011-03-14 15:25:47 UTC (rev 25372)
Changed blocks: 3, Lines Added: 35, Lines Deleted: 30; 3983 bytes

@@ -6028,6 +6028,36 @@
       </para>
 
       <para>
+        To apply <literal>ORDER BY</literal> or <literal>LIMIT</literal>
+        to an individual <literal role="stmt">SELECT</literal>, place
+        the clause inside the parentheses that enclose the
+        <literal role="stmt">SELECT</literal>:
+      </para>
+
+<programlisting>
+(SELECT a FROM t1 WHERE a=10 AND B=1 ORDER BY a LIMIT 10)
+UNION
+(SELECT a FROM t2 WHERE a=11 AND B=2 ORDER BY a LIMIT 10);
+</programlisting>
+
+      <para>
+        However, use of <literal>ORDER BY</literal> for individual
+        <literal role="stmt">SELECT</literal> statements implies nothing
+        about the order in which the rows appear in the final result
+        because <literal role="stmt">UNION</literal> by default produces
+        an unordered set of rows. Therefore, the use of <literal>ORDER
+        BY</literal> in this context is typically in conjunction with
+        <literal>LIMIT</literal>, so that it is used to determine the
+        subset of the selected rows to retrieve for the
+        <literal role="stmt">SELECT</literal>, even though it does not
+        necessarily affect the order of those rows in the final
+        <literal role="stmt">UNION</literal> result. If <literal>ORDER
+        BY</literal> appears without <literal>LIMIT</literal> in a
+        <literal role="stmt">SELECT</literal>, it is optimized away
+        because it will have no effect anyway.
+      </para>
+
+      <para>
         To use an <literal>ORDER BY</literal> or
         <literal>LIMIT</literal> clause to sort or limit the entire
         <literal role="stmt">UNION</literal> result, parenthesize the

@@ -6045,6 +6075,11 @@
 </programlisting>
 
       <para>
+        A statement without parentheses is equivalent to one
+        parenthesized as just shown.
+      </para>
+
+      <para>
         This kind of <literal>ORDER BY</literal> cannot use column
         references that include a table name (that is, names in
         <replaceable>tbl_name</replaceable>.<replaceable>col_name</replaceable>

@@ -6070,36 +6105,6 @@
 </programlisting>
 
       <para>
-        To apply <literal>ORDER BY</literal> or <literal>LIMIT</literal>
-        to an individual <literal role="stmt">SELECT</literal>, place
-        the clause inside the parentheses that enclose the
-        <literal role="stmt">SELECT</literal>:
-      </para>
-
-<programlisting>
-(SELECT a FROM t1 WHERE a=10 AND B=1 ORDER BY a LIMIT 10)
-UNION
-(SELECT a FROM t2 WHERE a=11 AND B=2 ORDER BY a LIMIT 10);
-</programlisting>
-
-      <para>
-        However, use of <literal>ORDER BY</literal> for individual
-        <literal role="stmt">SELECT</literal> statements implies nothing
-        about the order in which the rows appear in the final result
-        because <literal role="stmt">UNION</literal> by default produces
-        an unordered set of rows. Therefore, the use of <literal>ORDER
-        BY</literal> in this context is typically in conjunction with
-        <literal>LIMIT</literal>, so that it is used to determine the
-        subset of the selected rows to retrieve for the
-        <literal role="stmt">SELECT</literal>, even though it does not
-        necessarily affect the order of those rows in the final
-        <literal role="stmt">UNION</literal> result. If <literal>ORDER
-        BY</literal> appears without <literal>LIMIT</literal> in a
-        <literal role="stmt">SELECT</literal>, it is optimized away
-        because it will have no effect anyway.
-      </para>
-
-      <para>
         To cause rows in a <literal role="stmt">UNION</literal> result
         to consist of the sets of rows retrieved by each
         <literal role="stmt">SELECT</literal> one after the other,


Modified: trunk/refman-5.1/sql-syntax-data-manipulation.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-data-manipulation.xml	2011-03-14 15:03:40 UTC (rev 25371)
+++ trunk/refman-5.1/sql-syntax-data-manipulation.xml	2011-03-14 15:25:47 UTC (rev 25372)
Changed blocks: 3, Lines Added: 35, Lines Deleted: 30; 3983 bytes

@@ -6307,6 +6307,36 @@
       </para>
 
       <para>
+        To apply <literal>ORDER BY</literal> or <literal>LIMIT</literal>
+        to an individual <literal role="stmt">SELECT</literal>, place
+        the clause inside the parentheses that enclose the
+        <literal role="stmt">SELECT</literal>:
+      </para>
+
+<programlisting>
+(SELECT a FROM t1 WHERE a=10 AND B=1 ORDER BY a LIMIT 10)
+UNION
+(SELECT a FROM t2 WHERE a=11 AND B=2 ORDER BY a LIMIT 10);
+</programlisting>
+
+      <para>
+        However, use of <literal>ORDER BY</literal> for individual
+        <literal role="stmt">SELECT</literal> statements implies nothing
+        about the order in which the rows appear in the final result
+        because <literal role="stmt">UNION</literal> by default produces
+        an unordered set of rows. Therefore, the use of <literal>ORDER
+        BY</literal> in this context is typically in conjunction with
+        <literal>LIMIT</literal>, so that it is used to determine the
+        subset of the selected rows to retrieve for the
+        <literal role="stmt">SELECT</literal>, even though it does not
+        necessarily affect the order of those rows in the final
+        <literal role="stmt">UNION</literal> result. If <literal>ORDER
+        BY</literal> appears without <literal>LIMIT</literal> in a
+        <literal role="stmt">SELECT</literal>, it is optimized away
+        because it will have no effect anyway.
+      </para>
+
+      <para>
         To use an <literal>ORDER BY</literal> or
         <literal>LIMIT</literal> clause to sort or limit the entire
         <literal role="stmt">UNION</literal> result, parenthesize the

@@ -6324,6 +6354,11 @@
 </programlisting>
 
       <para>
+        A statement without parentheses is equivalent to one
+        parenthesized as just shown.
+      </para>
+
+      <para>
         This kind of <literal>ORDER BY</literal> cannot use column
         references that include a table name (that is, names in
         <replaceable>tbl_name</replaceable>.<replaceable>col_name</replaceable>

@@ -6349,36 +6384,6 @@
 </programlisting>
 
       <para>
-        To apply <literal>ORDER BY</literal> or <literal>LIMIT</literal>
-        to an individual <literal role="stmt">SELECT</literal>, place
-        the clause inside the parentheses that enclose the
-        <literal role="stmt">SELECT</literal>:
-      </para>
-
-<programlisting>
-(SELECT a FROM t1 WHERE a=10 AND B=1 ORDER BY a LIMIT 10)
-UNION
-(SELECT a FROM t2 WHERE a=11 AND B=2 ORDER BY a LIMIT 10);
-</programlisting>
-
-      <para>
-        However, use of <literal>ORDER BY</literal> for individual
-        <literal role="stmt">SELECT</literal> statements implies nothing
-        about the order in which the rows appear in the final result
-        because <literal role="stmt">UNION</literal> by default produces
-        an unordered set of rows. Therefore, the use of <literal>ORDER
-        BY</literal> in this context is typically in conjunction with
-        <literal>LIMIT</literal>, so that it is used to determine the
-        subset of the selected rows to retrieve for the
-        <literal role="stmt">SELECT</literal>, even though it does not
-        necessarily affect the order of those rows in the final
-        <literal role="stmt">UNION</literal> result. If <literal>ORDER
-        BY</literal> appears without <literal>LIMIT</literal> in a
-        <literal role="stmt">SELECT</literal>, it is optimized away
-        because it will have no effect anyway.
-      </para>
-
-      <para>
         To cause rows in a <literal role="stmt">UNION</literal> result
         to consist of the sets of rows retrieved by each
         <literal role="stmt">SELECT</literal> one after the other,


Modified: trunk/refman-5.5/sql-syntax-data-manipulation.xml
===================================================================
--- trunk/refman-5.5/sql-syntax-data-manipulation.xml	2011-03-14 15:03:40 UTC (rev 25371)
+++ trunk/refman-5.5/sql-syntax-data-manipulation.xml	2011-03-14 15:25:47 UTC (rev 25372)
Changed blocks: 3, Lines Added: 35, Lines Deleted: 30; 3983 bytes

@@ -6956,6 +6956,36 @@
       </para>
 
       <para>
+        To apply <literal>ORDER BY</literal> or <literal>LIMIT</literal>
+        to an individual <literal role="stmt">SELECT</literal>, place
+        the clause inside the parentheses that enclose the
+        <literal role="stmt">SELECT</literal>:
+      </para>
+
+<programlisting>
+(SELECT a FROM t1 WHERE a=10 AND B=1 ORDER BY a LIMIT 10)
+UNION
+(SELECT a FROM t2 WHERE a=11 AND B=2 ORDER BY a LIMIT 10);
+</programlisting>
+
+      <para>
+        However, use of <literal>ORDER BY</literal> for individual
+        <literal role="stmt">SELECT</literal> statements implies nothing
+        about the order in which the rows appear in the final result
+        because <literal role="stmt">UNION</literal> by default produces
+        an unordered set of rows. Therefore, the use of <literal>ORDER
+        BY</literal> in this context is typically in conjunction with
+        <literal>LIMIT</literal>, so that it is used to determine the
+        subset of the selected rows to retrieve for the
+        <literal role="stmt">SELECT</literal>, even though it does not
+        necessarily affect the order of those rows in the final
+        <literal role="stmt">UNION</literal> result. If <literal>ORDER
+        BY</literal> appears without <literal>LIMIT</literal> in a
+        <literal role="stmt">SELECT</literal>, it is optimized away
+        because it will have no effect anyway.
+      </para>
+
+      <para>
         To use an <literal>ORDER BY</literal> or
         <literal>LIMIT</literal> clause to sort or limit the entire
         <literal role="stmt">UNION</literal> result, parenthesize the

@@ -6973,6 +7003,11 @@
 </programlisting>
 
       <para>
+        A statement without parentheses is equivalent to one
+        parenthesized as just shown.
+      </para>
+
+      <para>
         This kind of <literal>ORDER BY</literal> cannot use column
         references that include a table name (that is, names in
         <replaceable>tbl_name</replaceable>.<replaceable>col_name</replaceable>

@@ -6998,36 +7033,6 @@
 </programlisting>
 
       <para>
-        To apply <literal>ORDER BY</literal> or <literal>LIMIT</literal>
-        to an individual <literal role="stmt">SELECT</literal>, place
-        the clause inside the parentheses that enclose the
-        <literal role="stmt">SELECT</literal>:
-      </para>
-
-<programlisting>
-(SELECT a FROM t1 WHERE a=10 AND B=1 ORDER BY a LIMIT 10)
-UNION
-(SELECT a FROM t2 WHERE a=11 AND B=2 ORDER BY a LIMIT 10);
-</programlisting>
-
-      <para>
-        However, use of <literal>ORDER BY</literal> for individual
-        <literal role="stmt">SELECT</literal> statements implies nothing
-        about the order in which the rows appear in the final result
-        because <literal role="stmt">UNION</literal> by default produces
-        an unordered set of rows. Therefore, the use of <literal>ORDER
-        BY</literal> in this context is typically in conjunction with
-        <literal>LIMIT</literal>, so that it is used to determine the
-        subset of the selected rows to retrieve for the
-        <literal role="stmt">SELECT</literal>, even though it does not
-        necessarily affect the order of those rows in the final
-        <literal role="stmt">UNION</literal> result. If <literal>ORDER
-        BY</literal> appears without <literal>LIMIT</literal> in a
-        <literal role="stmt">SELECT</literal>, it is optimized away
-        because it will have no effect anyway.
-      </para>
-
-      <para>
         To cause rows in a <literal role="stmt">UNION</literal> result
         to consist of the sets of rows retrieved by each
         <literal role="stmt">SELECT</literal> one after the other,


Modified: trunk/refman-5.6/sql-syntax-data-manipulation.xml
===================================================================
--- trunk/refman-5.6/sql-syntax-data-manipulation.xml	2011-03-14 15:03:40 UTC (rev 25371)
+++ trunk/refman-5.6/sql-syntax-data-manipulation.xml	2011-03-14 15:25:47 UTC (rev 25372)
Changed blocks: 3, Lines Added: 35, Lines Deleted: 30; 3983 bytes

@@ -6879,6 +6879,36 @@
       </para>
 
       <para>
+        To apply <literal>ORDER BY</literal> or <literal>LIMIT</literal>
+        to an individual <literal role="stmt">SELECT</literal>, place
+        the clause inside the parentheses that enclose the
+        <literal role="stmt">SELECT</literal>:
+      </para>
+
+<programlisting>
+(SELECT a FROM t1 WHERE a=10 AND B=1 ORDER BY a LIMIT 10)
+UNION
+(SELECT a FROM t2 WHERE a=11 AND B=2 ORDER BY a LIMIT 10);
+</programlisting>
+
+      <para>
+        However, use of <literal>ORDER BY</literal> for individual
+        <literal role="stmt">SELECT</literal> statements implies nothing
+        about the order in which the rows appear in the final result
+        because <literal role="stmt">UNION</literal> by default produces
+        an unordered set of rows. Therefore, the use of <literal>ORDER
+        BY</literal> in this context is typically in conjunction with
+        <literal>LIMIT</literal>, so that it is used to determine the
+        subset of the selected rows to retrieve for the
+        <literal role="stmt">SELECT</literal>, even though it does not
+        necessarily affect the order of those rows in the final
+        <literal role="stmt">UNION</literal> result. If <literal>ORDER
+        BY</literal> appears without <literal>LIMIT</literal> in a
+        <literal role="stmt">SELECT</literal>, it is optimized away
+        because it will have no effect anyway.
+      </para>
+
+      <para>
         To use an <literal>ORDER BY</literal> or
         <literal>LIMIT</literal> clause to sort or limit the entire
         <literal role="stmt">UNION</literal> result, parenthesize the

@@ -6896,6 +6926,11 @@
 </programlisting>
 
       <para>
+        A statement without parentheses is equivalent to one
+        parenthesized as just shown.
+      </para>
+
+      <para>
         This kind of <literal>ORDER BY</literal> cannot use column
         references that include a table name (that is, names in
         <replaceable>tbl_name</replaceable>.<replaceable>col_name</replaceable>

@@ -6921,36 +6956,6 @@
 </programlisting>
 
       <para>
-        To apply <literal>ORDER BY</literal> or <literal>LIMIT</literal>
-        to an individual <literal role="stmt">SELECT</literal>, place
-        the clause inside the parentheses that enclose the
-        <literal role="stmt">SELECT</literal>:
-      </para>
-
-<programlisting>
-(SELECT a FROM t1 WHERE a=10 AND B=1 ORDER BY a LIMIT 10)
-UNION
-(SELECT a FROM t2 WHERE a=11 AND B=2 ORDER BY a LIMIT 10);
-</programlisting>
-
-      <para>
-        However, use of <literal>ORDER BY</literal> for individual
-        <literal role="stmt">SELECT</literal> statements implies nothing
-        about the order in which the rows appear in the final result
-        because <literal role="stmt">UNION</literal> by default produces
-        an unordered set of rows. Therefore, the use of <literal>ORDER
-        BY</literal> in this context is typically in conjunction with
-        <literal>LIMIT</literal>, so that it is used to determine the
-        subset of the selected rows to retrieve for the
-        <literal role="stmt">SELECT</literal>, even though it does not
-        necessarily affect the order of those rows in the final
-        <literal role="stmt">UNION</literal> result. If <literal>ORDER
-        BY</literal> appears without <literal>LIMIT</literal> in a
-        <literal role="stmt">SELECT</literal>, it is optimized away
-        because it will have no effect anyway.
-      </para>
-
-      <para>
         To cause rows in a <literal role="stmt">UNION</literal> result
         to consist of the sets of rows retrieved by each
         <literal role="stmt">SELECT</literal> one after the other,


Modified: trunk/refman-6.0/sql-syntax-data-manipulation.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-data-manipulation.xml	2011-03-14 15:03:40 UTC (rev 25371)
+++ trunk/refman-6.0/sql-syntax-data-manipulation.xml	2011-03-14 15:25:47 UTC (rev 25372)
Changed blocks: 3, Lines Added: 35, Lines Deleted: 30; 3983 bytes

@@ -6939,6 +6939,36 @@
       </para>
 
       <para>
+        To apply <literal>ORDER BY</literal> or <literal>LIMIT</literal>
+        to an individual <literal role="stmt">SELECT</literal>, place
+        the clause inside the parentheses that enclose the
+        <literal role="stmt">SELECT</literal>:
+      </para>
+
+<programlisting>
+(SELECT a FROM t1 WHERE a=10 AND B=1 ORDER BY a LIMIT 10)
+UNION
+(SELECT a FROM t2 WHERE a=11 AND B=2 ORDER BY a LIMIT 10);
+</programlisting>
+
+      <para>
+        However, use of <literal>ORDER BY</literal> for individual
+        <literal role="stmt">SELECT</literal> statements implies nothing
+        about the order in which the rows appear in the final result
+        because <literal role="stmt">UNION</literal> by default produces
+        an unordered set of rows. Therefore, the use of <literal>ORDER
+        BY</literal> in this context is typically in conjunction with
+        <literal>LIMIT</literal>, so that it is used to determine the
+        subset of the selected rows to retrieve for the
+        <literal role="stmt">SELECT</literal>, even though it does not
+        necessarily affect the order of those rows in the final
+        <literal role="stmt">UNION</literal> result. If <literal>ORDER
+        BY</literal> appears without <literal>LIMIT</literal> in a
+        <literal role="stmt">SELECT</literal>, it is optimized away
+        because it will have no effect anyway.
+      </para>
+
+      <para>
         To use an <literal>ORDER BY</literal> or
         <literal>LIMIT</literal> clause to sort or limit the entire
         <literal role="stmt">UNION</literal> result, parenthesize the

@@ -6956,6 +6986,11 @@
 </programlisting>
 
       <para>
+        A statement without parentheses is equivalent to one
+        parenthesized as just shown.
+      </para>
+
+      <para>
         This kind of <literal>ORDER BY</literal> cannot use column
         references that include a table name (that is, names in
         <replaceable>tbl_name</replaceable>.<replaceable>col_name</replaceable>

@@ -6981,36 +7016,6 @@
 </programlisting>
 
       <para>
-        To apply <literal>ORDER BY</literal> or <literal>LIMIT</literal>
-        to an individual <literal role="stmt">SELECT</literal>, place
-        the clause inside the parentheses that enclose the
-        <literal role="stmt">SELECT</literal>:
-      </para>
-
-<programlisting>
-(SELECT a FROM t1 WHERE a=10 AND B=1 ORDER BY a LIMIT 10)
-UNION
-(SELECT a FROM t2 WHERE a=11 AND B=2 ORDER BY a LIMIT 10);
-</programlisting>
-
-      <para>
-        However, use of <literal>ORDER BY</literal> for individual
-        <literal role="stmt">SELECT</literal> statements implies nothing
-        about the order in which the rows appear in the final result
-        because <literal role="stmt">UNION</literal> by default produces
-        an unordered set of rows. Therefore, the use of <literal>ORDER
-        BY</literal> in this context is typically in conjunction with
-        <literal>LIMIT</literal>, so that it is used to determine the
-        subset of the selected rows to retrieve for the
-        <literal role="stmt">SELECT</literal>, even though it does not
-        necessarily affect the order of those rows in the final
-        <literal role="stmt">UNION</literal> result. If <literal>ORDER
-        BY</literal> appears without <literal>LIMIT</literal> in a
-        <literal role="stmt">SELECT</literal>, it is optimized away
-        because it will have no effect anyway.
-      </para>
-
-      <para>
         To cause rows in a <literal role="stmt">UNION</literal> result
         to consist of the sets of rows retrieved by each
         <literal role="stmt">SELECT</literal> one after the other,


Thread
svn commit - mysqldoc@oter02: r25372 - in trunk: . refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0paul.dubois14 Mar