Author: paul
Date: 2008-09-03 22:34:46 +0200 (Wed, 03 Sep 2008)
New Revision: 11659
Log:
r32972@arctic: paul | 2008-09-03 15:35:52 -0500
sql_select_limit is not a session-only variable. It has a global value.
Modified:
trunk/refman-4.1/dba-core.xml
trunk/refman-5.0/dba-core.xml
trunk/refman-5.1/dba-core.xml
trunk/refman-6.0/dba-core.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:33589
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:32970
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:33589
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:32972
Modified: trunk/refman-4.1/dba-core.xml
===================================================================
--- trunk/refman-4.1/dba-core.xml 2008-09-03 20:05:58 UTC (rev 11658)
+++ trunk/refman-4.1/dba-core.xml 2008-09-03 20:34:46 UTC (rev 11659)
Changed blocks: 3, Lines Added: 39, Lines Deleted: 43; 4338 bytes
@@ -5935,6 +5935,45 @@
</listitem>
<listitem>
+ <para id="option_mysqld_sql_select_limit">
+ <literal>sql_select_limit</literal>
+ </para>
+
+ <para condition="dynamic:optvar:item" role="5.0:mysqld:sql_select_limit"/>
+
+ <para>
+ The maximum number of rows to return from
+ <literal>SELECT</literal> statements. The default value for
+ a new connection is the maximum number of rows that the
+ server allows per table, which depends on the server
+ configuration and may be affected if the server build was
+ configured with <option>--with-big-tables</option>. Typical
+ default values are (2<superscript>32</superscript>)−1
+ or (2<superscript>64</superscript>)−1. If you have
+ changed the limit, the default value can be restored by
+ assigning a value of <literal>DEFAULT</literal>.
+ </para>
+
+ <para>
+ If a <literal>SELECT</literal> has a
+ <literal>LIMIT</literal> clause, the
+ <literal>LIMIT</literal> takes precedence over the value of
+ <literal>sql_select_limit</literal>.
+ </para>
+
+ <para>
+ <literal>sql_select_limit</literal> does not apply to
+ <literal>SELECT</literal> statements executed within stored
+ routines. It also does not apply to
+ <literal>SELECT</literal> statements that do not produce a
+ result set to be returned to the client. These include
+ <literal>SELECT</literal> statements in subqueries,
+ <literal>CREATE TABLE ... SELECT</literal>, and
+ <literal>INSERT INTO ... SELECT</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
<para id="option_mysqld_sql_slave_skip_counter">
<literal>sql_slave_skip_counter</literal>
</para>
@@ -6532,11 +6571,6 @@
<indexterm>
<primary>SET</primary>
- <secondary>SQL_SELECT_LIMIT</secondary>
- </indexterm>
-
- <indexterm>
- <primary>SET</primary>
<secondary>SQL_WARNINGS</secondary>
</indexterm>
@@ -6885,44 +6919,6 @@
</listitem>
<listitem>
- <para id="option_mysqld_sql_select_limit">
- <literal>SQL_SELECT_LIMIT =
- {<replaceable>value</replaceable> | DEFAULT}</literal>
- </para>
-
- <para>
- The maximum number of rows to return from
- <literal>SELECT</literal> statements. The default value for
- a new connection is the maximum number of rows that the
- server allows per table, which depends on the server
- configuration and may be affected if the server build was
- configured with <option>--with-big-tables</option>. Typical
- default values are (2<superscript>32</superscript>)−1
- or (2<superscript>64</superscript>)−1. If you have
- changed the limit, the default value can be restored by
- assigning a value of <literal>DEFAULT</literal>.
- </para>
-
- <para>
- If a <literal>SELECT</literal> has a
- <literal>LIMIT</literal> clause, the
- <literal>LIMIT</literal> takes precedence over the value of
- <literal>SQL_SELECT_LIMIT</literal>.
- </para>
-
- <para>
- <literal>SQL_SELECT_LIMIT</literal> does not apply to
- <literal>SELECT</literal> statements executed within stored
- routines. It also does not apply to
- <literal>SELECT</literal> statements that do not produce a
- result set to be returned to the client. These include
- <literal>SELECT</literal> statements in subqueries,
- <literal>CREATE TABLE ... SELECT</literal>, and
- <literal>INSERT INTO ... SELECT</literal>.
- </para>
- </listitem>
-
- <listitem>
<para id="option_mysqld_sql_warnings">
<literal>SQL_WARNINGS = {0 | 1}</literal>
</para>
Modified: trunk/refman-5.0/dba-core.xml
===================================================================
--- trunk/refman-5.0/dba-core.xml 2008-09-03 20:05:58 UTC (rev 11658)
+++ trunk/refman-5.0/dba-core.xml 2008-09-03 20:34:46 UTC (rev 11659)
Changed blocks: 3, Lines Added: 39, Lines Deleted: 43; 4338 bytes
@@ -7011,6 +7011,45 @@
</listitem>
<listitem>
+ <para id="option_mysqld_sql_select_limit">
+ <literal>sql_select_limit</literal>
+ </para>
+
+ <para condition="dynamic:optvar:item" role="5.0:mysqld:sql_select_limit"/>
+
+ <para>
+ The maximum number of rows to return from
+ <literal>SELECT</literal> statements. The default value for
+ a new connection is the maximum number of rows that the
+ server allows per table, which depends on the server
+ configuration and may be affected if the server build was
+ configured with <option>--with-big-tables</option>. Typical
+ default values are (2<superscript>32</superscript>)−1
+ or (2<superscript>64</superscript>)−1. If you have
+ changed the limit, the default value can be restored by
+ assigning a value of <literal>DEFAULT</literal>.
+ </para>
+
+ <para>
+ If a <literal>SELECT</literal> has a
+ <literal>LIMIT</literal> clause, the
+ <literal>LIMIT</literal> takes precedence over the value of
+ <literal>sql_select_limit</literal>.
+ </para>
+
+ <para>
+ <literal>sql_select_limit</literal> does not apply to
+ <literal>SELECT</literal> statements executed within stored
+ routines. It also does not apply to
+ <literal>SELECT</literal> statements that do not produce a
+ result set to be returned to the client. These include
+ <literal>SELECT</literal> statements in subqueries,
+ <literal>CREATE TABLE ... SELECT</literal>, and
+ <literal>INSERT INTO ... SELECT</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
<para id="option_mysqld_sql_slave_skip_counter">
<literal>sql_slave_skip_counter</literal>
</para>
@@ -7794,11 +7833,6 @@
<indexterm>
<primary>SET</primary>
- <secondary>SQL_SELECT_LIMIT</secondary>
- </indexterm>
-
- <indexterm>
- <primary>SET</primary>
<secondary>SQL_WARNINGS</secondary>
</indexterm>
@@ -8169,44 +8203,6 @@
</listitem>
<listitem>
- <para id="option_mysqld_sql_select_limit">
- <literal>SQL_SELECT_LIMIT =
- {<replaceable>value</replaceable> | DEFAULT}</literal>
- </para>
-
- <para>
- The maximum number of rows to return from
- <literal>SELECT</literal> statements. The default value for
- a new connection is the maximum number of rows that the
- server allows per table, which depends on the server
- configuration and may be affected if the server build was
- configured with <option>--with-big-tables</option>. Typical
- default values are (2<superscript>32</superscript>)−1
- or (2<superscript>64</superscript>)−1. If you have
- changed the limit, the default value can be restored by
- assigning a value of <literal>DEFAULT</literal>.
- </para>
-
- <para>
- If a <literal>SELECT</literal> has a
- <literal>LIMIT</literal> clause, the
- <literal>LIMIT</literal> takes precedence over the value of
- <literal>SQL_SELECT_LIMIT</literal>.
- </para>
-
- <para>
- <literal>SQL_SELECT_LIMIT</literal> does not apply to
- <literal>SELECT</literal> statements executed within stored
- routines. It also does not apply to
- <literal>SELECT</literal> statements that do not produce a
- result set to be returned to the client. These include
- <literal>SELECT</literal> statements in subqueries,
- <literal>CREATE TABLE ... SELECT</literal>, and
- <literal>INSERT INTO ... SELECT</literal>.
- </para>
- </listitem>
-
- <listitem>
<para id="option_mysqld_sql_warnings">
<literal>SQL_WARNINGS = {0 | 1}</literal>
</para>
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2008-09-03 20:05:58 UTC (rev 11658)
+++ trunk/refman-5.1/dba-core.xml 2008-09-03 20:34:46 UTC (rev 11659)
Changed blocks: 4, Lines Added: 46, Lines Deleted: 50; 5315 bytes
@@ -7472,6 +7472,45 @@
</listitem>
<listitem>
+ <para id="option_mysqld_sql_select_limit">
+ <literal>sql_select_limit</literal>
+ </para>
+
+ <para condition="dynamic:optvar:item" role="5.1:mysqld:sql_select_limit"/>
+
+ <para>
+ The maximum number of rows to return from
+ <literal>SELECT</literal> statements. The default value for
+ a new connection is the maximum number of rows that the
+ server allows per table, which depends on the server
+ configuration and may be affected if the server build was
+ configured with <option>--with-big-tables</option>. Typical
+ default values are (2<superscript>32</superscript>)−1
+ or (2<superscript>64</superscript>)−1. If you have
+ changed the limit, the default value can be restored by
+ assigning a value of <literal>DEFAULT</literal>.
+ </para>
+
+ <para>
+ If a <literal>SELECT</literal> has a
+ <literal>LIMIT</literal> clause, the
+ <literal>LIMIT</literal> takes precedence over the value of
+ <literal>sql_select_limit</literal>.
+ </para>
+
+ <para>
+ <literal>sql_select_limit</literal> does not apply to
+ <literal>SELECT</literal> statements executed within stored
+ routines. It also does not apply to
+ <literal>SELECT</literal> statements that do not produce a
+ result set to be returned to the client. These include
+ <literal>SELECT</literal> statements in subqueries,
+ <literal>CREATE TABLE ... SELECT</literal>, and
+ <literal>INSERT INTO ... SELECT</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
<para id="option_mysqld_sql_slave_skip_counter">
<literal>sql_slave_skip_counter</literal>
</para>
@@ -8258,11 +8297,6 @@
<indexterm>
<primary>SET</primary>
- <secondary>SQL_SELECT_LIMIT</secondary>
- </indexterm>
-
- <indexterm>
- <primary>SET</primary>
<secondary>SQL_WARNINGS</secondary>
</indexterm>
@@ -8599,44 +8633,6 @@
</listitem>
<listitem>
- <para id="option_mysqld_sql_select_limit">
- <literal>SQL_SELECT_LIMIT =
- {<replaceable>value</replaceable> | DEFAULT}</literal>
- </para>
-
- <para>
- The maximum number of rows to return from
- <literal>SELECT</literal> statements. The default value for
- a new connection is the maximum number of rows that the
- server allows per table, which depends on the server
- configuration and may be affected if the server build was
- configured with <option>--with-big-tables</option>. Typical
- default values are (2<superscript>32</superscript>)−1
- or (2<superscript>64</superscript>)−1. If you have
- changed the limit, the default value can be restored by
- assigning a value of <literal>DEFAULT</literal>.
- </para>
-
- <para>
- If a <literal>SELECT</literal> has a
- <literal>LIMIT</literal> clause, the
- <literal>LIMIT</literal> takes precedence over the value of
- <literal>SQL_SELECT_LIMIT</literal>.
- </para>
-
- <para>
- <literal>SQL_SELECT_LIMIT</literal> does not apply to
- <literal>SELECT</literal> statements executed within stored
- routines. It also does not apply to
- <literal>SELECT</literal> statements that do not produce a
- result set to be returned to the client. These include
- <literal>SELECT</literal> statements in subqueries,
- <literal>CREATE TABLE ... SELECT</literal>, and
- <literal>INSERT INTO ... SELECT</literal>.
- </para>
- </listitem>
-
- <listitem>
<para id="option_mysqld_sql_warnings">
<literal>SQL_WARNINGS = {0 | 1}</literal>
</para>
@@ -12681,13 +12677,13 @@
<listitem>
<para>
- Log contents are accessible via SQL statements. This
- enables the use of queries that select only those log
- entries that satisfy specific criteria. For example, to
- select log contents associated with a particular client
- (which can be useful for identifying problematic queries
- from that client), it is easier to do this using a log table
- than a log file.
+ Log contents are accessible via SQL statements. This enables
+ the use of queries that select only those log entries that
+ satisfy specific criteria. For example, to select log
+ contents associated with a particular client (which can be
+ useful for identifying problematic queries from that
+ client), it is easier to do this using a log table than a
+ log file.
</para>
</listitem>
Modified: trunk/refman-6.0/dba-core.xml
===================================================================
--- trunk/refman-6.0/dba-core.xml 2008-09-03 20:05:58 UTC (rev 11658)
+++ trunk/refman-6.0/dba-core.xml 2008-09-03 20:34:46 UTC (rev 11659)
Changed blocks: 4, Lines Added: 46, Lines Deleted: 50; 5315 bytes
@@ -7338,6 +7338,45 @@
</listitem>
<listitem>
+ <para id="option_mysqld_sql_select_limit">
+ <literal>sql_select_limit</literal>
+ </para>
+
+ <para condition="dynamic:optvar:item" role="6.0:mysqld:sql_select_limit"/>
+
+ <para>
+ The maximum number of rows to return from
+ <literal>SELECT</literal> statements. The default value for
+ a new connection is the maximum number of rows that the
+ server allows per table, which depends on the server
+ configuration and may be affected if the server build was
+ configured with <option>--with-big-tables</option>. Typical
+ default values are (2<superscript>32</superscript>)−1
+ or (2<superscript>64</superscript>)−1. If you have
+ changed the limit, the default value can be restored by
+ assigning a value of <literal>DEFAULT</literal>.
+ </para>
+
+ <para>
+ If a <literal>SELECT</literal> has a
+ <literal>LIMIT</literal> clause, the
+ <literal>LIMIT</literal> takes precedence over the value of
+ <literal>sql_select_limit</literal>.
+ </para>
+
+ <para>
+ <literal>sql_select_limit</literal> does not apply to
+ <literal>SELECT</literal> statements executed within stored
+ routines. It also does not apply to
+ <literal>SELECT</literal> statements that do not produce a
+ result set to be returned to the client. These include
+ <literal>SELECT</literal> statements in subqueries,
+ <literal>CREATE TABLE ... SELECT</literal>, and
+ <literal>INSERT INTO ... SELECT</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
<para id="option_mysqld_sql_slave_skip_counter">
<literal>sql_slave_skip_counter</literal>
</para>
@@ -8128,11 +8167,6 @@
<indexterm>
<primary>SET</primary>
- <secondary>SQL_SELECT_LIMIT</secondary>
- </indexterm>
-
- <indexterm>
- <primary>SET</primary>
<secondary>SQL_WARNINGS</secondary>
</indexterm>
@@ -8500,44 +8534,6 @@
</listitem>
<listitem>
- <para id="option_mysqld_sql_select_limit">
- <literal>SQL_SELECT_LIMIT =
- {<replaceable>value</replaceable> | DEFAULT}</literal>
- </para>
-
- <para>
- The maximum number of rows to return from
- <literal>SELECT</literal> statements. The default value for
- a new connection is the maximum number of rows that the
- server allows per table, which depends on the server
- configuration and may be affected if the server build was
- configured with <option>--with-big-tables</option>. Typical
- default values are (2<superscript>32</superscript>)−1
- or (2<superscript>64</superscript>)−1. If you have
- changed the limit, the default value can be restored by
- assigning a value of <literal>DEFAULT</literal>.
- </para>
-
- <para>
- If a <literal>SELECT</literal> has a
- <literal>LIMIT</literal> clause, the
- <literal>LIMIT</literal> takes precedence over the value of
- <literal>SQL_SELECT_LIMIT</literal>.
- </para>
-
- <para>
- <literal>SQL_SELECT_LIMIT</literal> does not apply to
- <literal>SELECT</literal> statements executed within stored
- routines. It also does not apply to
- <literal>SELECT</literal> statements that do not produce a
- result set to be returned to the client. These include
- <literal>SELECT</literal> statements in subqueries,
- <literal>CREATE TABLE ... SELECT</literal>, and
- <literal>INSERT INTO ... SELECT</literal>.
- </para>
- </listitem>
-
- <listitem>
<para id="option_mysqld_sql_warnings">
<literal>SQL_WARNINGS = {0 | 1}</literal>
</para>
@@ -12584,13 +12580,13 @@
<listitem>
<para>
- Log contents are accessible via SQL statements. This
- enables the use of queries that select only those log
- entries that satisfy specific criteria. For example, to
- select log contents associated with a particular client
- (which can be useful for identifying problematic queries
- from that client), it is easier to do this using a log table
- than a log file.
+ Log contents are accessible via SQL statements. This enables
+ the use of queries that select only those log entries that
+ satisfy specific criteria. For example, to select log
+ contents associated with a particular client (which can be
+ useful for identifying problematic queries from that
+ client), it is easier to do this using a log table than a
+ log file.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r11659 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-6.0 | paul.dubois | 3 Sep |
