Below is the list of changes that have just been committed into a local
mysqldoc repository of jon. When jon 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.2870 05/06/24 17:37:56 jon@stripped +6 -0
news-5-0-7, mysql-database-administration:
Change in scope and default value of
Last_query_cost system variable.
Sync refman-4.1 and refman-5.0 subtrees to refman.
refman/news.xml
1.29 05/06/24 17:37:54 jon@stripped +15 -6
5.0.7 changelog: Change in scope
and default value of Last_query_cost
system variable.
refman/mysql-database-administration.xml
1.7 05/06/24 17:37:54 jon@stripped +13 -11
Change in scope and default value of
Last_query_cost system variable.
refman-5.0/news.xml
1.24 05/06/24 17:37:53 jon@stripped +15 -6
Sync with refman tree.
refman-5.0/mysql-database-administration.xml
1.5 05/06/24 17:37:53 jon@stripped +13 -11
Sync with refman tree.
refman-4.1/news.xml
1.24 05/06/24 17:37:53 jon@stripped +15 -6
Sync with refman tree.
refman-4.1/mysql-database-administration.xml
1.5 05/06/24 17:37:52 jon@stripped +13 -11
Sync with refman tree.
# 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: jon
# Host: gigan.site
# Root: /home/jon/bk/mysqldoc
--- 1.4/refman-4.1/mysql-database-administration.xml 2005-06-21 21:18:34 +10:00
+++ 1.5/refman-4.1/mysql-database-administration.xml 2005-06-24 17:37:52 +10:00
@@ -9325,8 +9325,8 @@
respectively.
<!--
- Additionally, the values of the older (available since MySQL 4.1.3)
- statement counter variables <literal>Com_prepare_sql</literal>,
+ Additionally, the values of the older (available since MySQL 4.1.3)
+ statement counter variables <literal>Com_prepare_sql</literal>,
<literal>Com_execute_sql</literal>, and
<literal>Com_deallocate_sql</literal> are increased for
the <literal>PREPARE</literal>, <literal>EXECUTE</literal>, and
@@ -9987,16 +9987,18 @@
The number of physical writes of a key block to disk.
</para></listitem>
- <listitem><para>
- <literal>Last_query_cost</literal>
- </para>
+ <listitem>
+ <para><literal>Last_query_cost</literal></para>
- <para>
- The total cost of the last compiled query as computed by the query
- optimizer. Useful for comparing the cost of different query plans
- for the same query. The default value of -1 means that no query has
- been compiled yet. This variable was added in MySQL 5.0.1.
- </para></listitem>
+ <para>The total cost of the last compiled query as computed by the
+ query optimizer. Useful for comparing the cost of different query
+ plans for the same query. The default value of 0 means that no
+ query has been compiled yet. This variable was added in MySQL
+ 5.0.1, with a default value of -1. In MySQL 5.0.7, the default was
+ changed to 0; also in version 5.0.7, the scope of
+ <literal>Last_query_cost</literal> was changed to session rather
+ than a global.</para>
+ </listitem>
<listitem><para>
<literal>Max_used_connections</literal>
--- 1.23/refman-4.1/news.xml 2005-06-24 14:28:26 +10:00
+++ 1.24/refman-4.1/news.xml 2005-06-24 17:37:53 +10:00
@@ -734,12 +734,21 @@
<itemizedlist>
- <listitem><para>
- Everything you write after the <literal>DELIMITER</literal> keyword
- will be set as delimiter. Ex: <literal>DELIMITER :;</literal> will
- set <literal>:;</literal> as the delimiter. This behavior is now
- consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879)
- </para></listitem>
+ <listitem>
+ <para>The behaviour of the <literal>Last_query_cost</literal>
+ system variable has been changed. The default value is now 0
+ (rather than -1) and it now has session-level scope (rather than
+ being global). See <xref linkend="server-status-variables"/> for
+ additional information.</para>
+ </listitem>
+
+ <listitem>
+ <para>All characters occuring on the same line following the
+ <literal>DELIMITER</literal> keyword will be set as delimiter. For
+ example, <literal>DELIMITER :;</literal> will set
+ <literal>:;</literal> as the delimiter. This behavior is now
+ consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879)</para>
+ </listitem>
<listitem><para>
The <literal>table</literal>, <literal>type</literal>, and
--- 1.4/refman-5.0/mysql-database-administration.xml 2005-06-21 21:18:36 +10:00
+++ 1.5/refman-5.0/mysql-database-administration.xml 2005-06-24 17:37:53 +10:00
@@ -9325,8 +9325,8 @@
respectively.
<!--
- Additionally, the values of the older (available since MySQL 4.1.3)
- statement counter variables <literal>Com_prepare_sql</literal>,
+ Additionally, the values of the older (available since MySQL 4.1.3)
+ statement counter variables <literal>Com_prepare_sql</literal>,
<literal>Com_execute_sql</literal>, and
<literal>Com_deallocate_sql</literal> are increased for
the <literal>PREPARE</literal>, <literal>EXECUTE</literal>, and
@@ -9987,16 +9987,18 @@
The number of physical writes of a key block to disk.
</para></listitem>
- <listitem><para>
- <literal>Last_query_cost</literal>
- </para>
+ <listitem>
+ <para><literal>Last_query_cost</literal></para>
- <para>
- The total cost of the last compiled query as computed by the query
- optimizer. Useful for comparing the cost of different query plans
- for the same query. The default value of -1 means that no query has
- been compiled yet. This variable was added in MySQL 5.0.1.
- </para></listitem>
+ <para>The total cost of the last compiled query as computed by the
+ query optimizer. Useful for comparing the cost of different query
+ plans for the same query. The default value of 0 means that no
+ query has been compiled yet. This variable was added in MySQL
+ 5.0.1, with a default value of -1. In MySQL 5.0.7, the default was
+ changed to 0; also in version 5.0.7, the scope of
+ <literal>Last_query_cost</literal> was changed to session rather
+ than a global.</para>
+ </listitem>
<listitem><para>
<literal>Max_used_connections</literal>
--- 1.23/refman-5.0/news.xml 2005-06-24 14:28:26 +10:00
+++ 1.24/refman-5.0/news.xml 2005-06-24 17:37:53 +10:00
@@ -734,12 +734,21 @@
<itemizedlist>
- <listitem><para>
- Everything you write after the <literal>DELIMITER</literal> keyword
- will be set as delimiter. Ex: <literal>DELIMITER :;</literal> will
- set <literal>:;</literal> as the delimiter. This behavior is now
- consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879)
- </para></listitem>
+ <listitem>
+ <para>The behaviour of the <literal>Last_query_cost</literal>
+ system variable has been changed. The default value is now 0
+ (rather than -1) and it now has session-level scope (rather than
+ being global). See <xref linkend="server-status-variables"/> for
+ additional information.</para>
+ </listitem>
+
+ <listitem>
+ <para>All characters occuring on the same line following the
+ <literal>DELIMITER</literal> keyword will be set as delimiter. For
+ example, <literal>DELIMITER :;</literal> will set
+ <literal>:;</literal> as the delimiter. This behavior is now
+ consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879)</para>
+ </listitem>
<listitem><para>
The <literal>table</literal>, <literal>type</literal>, and
--- 1.6/refman/mysql-database-administration.xml 2005-06-21 21:17:45 +10:00
+++ 1.7/refman/mysql-database-administration.xml 2005-06-24 17:37:54 +10:00
@@ -9325,8 +9325,8 @@
respectively.
<!--
- Additionally, the values of the older (available since MySQL 4.1.3)
- statement counter variables <literal>Com_prepare_sql</literal>,
+ Additionally, the values of the older (available since MySQL 4.1.3)
+ statement counter variables <literal>Com_prepare_sql</literal>,
<literal>Com_execute_sql</literal>, and
<literal>Com_deallocate_sql</literal> are increased for
the <literal>PREPARE</literal>, <literal>EXECUTE</literal>, and
@@ -9987,16 +9987,18 @@
The number of physical writes of a key block to disk.
</para></listitem>
- <listitem><para>
- <literal>Last_query_cost</literal>
- </para>
+ <listitem>
+ <para><literal>Last_query_cost</literal></para>
- <para>
- The total cost of the last compiled query as computed by the query
- optimizer. Useful for comparing the cost of different query plans
- for the same query. The default value of -1 means that no query has
- been compiled yet. This variable was added in MySQL 5.0.1.
- </para></listitem>
+ <para>The total cost of the last compiled query as computed by the
+ query optimizer. Useful for comparing the cost of different query
+ plans for the same query. The default value of 0 means that no
+ query has been compiled yet. This variable was added in MySQL
+ 5.0.1, with a default value of -1. In MySQL 5.0.7, the default was
+ changed to 0; also in version 5.0.7, the scope of
+ <literal>Last_query_cost</literal> was changed to session rather
+ than a global.</para>
+ </listitem>
<listitem><para>
<literal>Max_used_connections</literal>
--- 1.28/refman/news.xml 2005-06-24 14:28:27 +10:00
+++ 1.29/refman/news.xml 2005-06-24 17:37:54 +10:00
@@ -734,12 +734,21 @@
<itemizedlist>
- <listitem><para>
- Everything you write after the <literal>DELIMITER</literal> keyword
- will be set as delimiter. Ex: <literal>DELIMITER :;</literal> will
- set <literal>:;</literal> as the delimiter. This behavior is now
- consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879)
- </para></listitem>
+ <listitem>
+ <para>The behaviour of the <literal>Last_query_cost</literal>
+ system variable has been changed. The default value is now 0
+ (rather than -1) and it now has session-level scope (rather than
+ being global). See <xref linkend="server-status-variables"/> for
+ additional information.</para>
+ </listitem>
+
+ <listitem>
+ <para>All characters occuring on the same line following the
+ <literal>DELIMITER</literal> keyword will be set as delimiter. For
+ example, <literal>DELIMITER :;</literal> will set
+ <literal>:;</literal> as the delimiter. This behavior is now
+ consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879)</para>
+ </listitem>
<listitem><para>
The <literal>table</literal>, <literal>type</literal>, and
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (jon:1.2870) | jon | 24 Jun |
