bk commit - mysqldoc@docsrva tree (stefan:1.2818)

[stefan]

Below is the list of changes that have just been committed into a local
mysqldoc repository of stefan. When stefan 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.2818 05/06/17 21:42:52 stefan@stripped +2 -0
  mysql-database-administration.xml:
    Sync changes

  refman-5.0/mysql-database-administration.xml
    1.3 05/06/17 21:42:34 stefan@stripped +68 -12
    Sync changes

  refman-4.1/mysql-database-administration.xml
    1.3 05/06/17 21:42:15 stefan@stripped +68 -12
    Sync changes

# 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:	stefan
# Host:	apollon.site
# Root:	/home/stefan/bk/mysqldoc

--- 1.2/refman-4.1/mysql-database-administration.xml	2005-06-17 05:14:50 +02:00
+++ 1.3/refman-4.1/mysql-database-administration.xml	2005-06-17 21:42:15 +02:00
@@ -9310,17 +9310,73 @@
      MySQL 3.23.7.
     </para></listitem>
 
-    <listitem><para>
-     <literal>Com_<replaceable>xxx</replaceable></literal>
-    </para>
-
-    <para>
-     The number of times each <replaceable>xxx</replaceable> statement
-     has been executed. There is one status variable for each type of
-     statement. For example, <literal>Com_delete</literal> and
-     <literal>Com_insert</literal> count
<literal>DELETE</literal> and
-     <literal>INSERT</literal> statements.
-    </para></listitem>
+    <listitem>
+     <para>
+      <literal>Com_<replaceable>xxx</replaceable></literal>
+     </para>
+     <para>
+      The <literal>Com_<replaceable>xxx</replaceable></literal>
statement
+      counter variables were added beginning with MySQL 3.23.47.
+      They indicate the number of times each <replaceable>xxx</replaceable> 
+      statement has been executed. There is one status variable for each type of
+      statement. For example, <literal>Com_delete</literal> and
+      <literal>Com_insert</literal> count
<literal>DELETE</literal> and
+      <literal>INSERT</literal> statements.
+     </para>
+     <para>
+      New
<literal>Com_stmt_<replaceable>xxx</replaceable></literal> status
variables 
+      have been added in MySQL 4.1.13 or 5.0.8, respectively.
+      <itemizedlist>
+       <listitem><para>
+        <literal>Com_stmt_prepare</literal>
+       </para></listitem>
+       <listitem><para>
+        <literal>Com_stmt_execute</literal>
+       </para></listitem>
+       <listitem><para>
+        <literal>Com_stmt_fetch</literal> (not available in versions before
5.0)
+       </para></listitem>
+       <listitem><para>
+        <literal>Com_stmt_send_long_data</literal>
+       </para></listitem>
+       <listitem><para>
+        <literal>Com_stmt_reset</literal>
+       </para></listitem>
+       <listitem><para>
+        <literal>Com_stmt_close</literal>
+       </para></listitem>
+      </itemizedlist>
+      Those variables stand for prepared statements commands. Their names 
+      refer to the
<literal>COM_<replaceable>xxx</replaceable></literal> command 
+      set used in the network layer; in other words: Their values are being
+      increased whenever prepared statements API calls such as 
+      <command>mysql_stmt_prepare()</command>,
+      <command>mysql_stmt_execute()</command>, and so forth are executed.
+      However, <literal>Com_stmt_prepare</literal>, 
+      <literal>Com_stmt_execute</literal> and 
+      <literal>Com_stmt_close</literal> are also increased when one issues 
+      the following SQL statements: <literal>PREPARE</literal>, 
+      <literal>EXECUTE</literal>, or
<literal>DEALLOCATE</literal>
+      respectively.
+      <!--
+      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
+      <literal>DEALLOCATE</literal> statements.
+      -->
+      <literal>Com_stmt_fetch</literal> stands for the total number of
network 
+      round-trips issued when fetching from cursors.
+     </para>
+     <para>
+      All of the
<literal>Com_stmt_<replaceable>xxx</replaceable></literal>
+      variables are increased even if their argument (a prepared statement) is 
+      unknown or an error occurred during execution; in other words: Their 
+      values correspond to the number of requests issued, not to the number of
+      requests successfully completed.
+     </para>
+    </listitem>
 
     <listitem><para>
      <literal>Connections</literal>
@@ -9970,7 +10026,7 @@
     <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
+     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>
 

--- 1.2/refman-5.0/mysql-database-administration.xml	2005-06-17 05:14:52 +02:00
+++ 1.3/refman-5.0/mysql-database-administration.xml	2005-06-17 21:42:34 +02:00
@@ -9310,17 +9310,73 @@
      MySQL 3.23.7.
     </para></listitem>
 
-    <listitem><para>
-     <literal>Com_<replaceable>xxx</replaceable></literal>
-    </para>
-
-    <para>
-     The number of times each <replaceable>xxx</replaceable> statement
-     has been executed. There is one status variable for each type of
-     statement. For example, <literal>Com_delete</literal> and
-     <literal>Com_insert</literal> count
<literal>DELETE</literal> and
-     <literal>INSERT</literal> statements.
-    </para></listitem>
+    <listitem>
+     <para>
+      <literal>Com_<replaceable>xxx</replaceable></literal>
+     </para>
+     <para>
+      The <literal>Com_<replaceable>xxx</replaceable></literal>
statement
+      counter variables were added beginning with MySQL 3.23.47.
+      They indicate the number of times each <replaceable>xxx</replaceable> 
+      statement has been executed. There is one status variable for each type of
+      statement. For example, <literal>Com_delete</literal> and
+      <literal>Com_insert</literal> count
<literal>DELETE</literal> and
+      <literal>INSERT</literal> statements.
+     </para>
+     <para>
+      New
<literal>Com_stmt_<replaceable>xxx</replaceable></literal> status
variables 
+      have been added in MySQL 4.1.13 or 5.0.8, respectively.
+      <itemizedlist>
+       <listitem><para>
+        <literal>Com_stmt_prepare</literal>
+       </para></listitem>
+       <listitem><para>
+        <literal>Com_stmt_execute</literal>
+       </para></listitem>
+       <listitem><para>
+        <literal>Com_stmt_fetch</literal> (not available in versions before
5.0)
+       </para></listitem>
+       <listitem><para>
+        <literal>Com_stmt_send_long_data</literal>
+       </para></listitem>
+       <listitem><para>
+        <literal>Com_stmt_reset</literal>
+       </para></listitem>
+       <listitem><para>
+        <literal>Com_stmt_close</literal>
+       </para></listitem>
+      </itemizedlist>
+      Those variables stand for prepared statements commands. Their names 
+      refer to the
<literal>COM_<replaceable>xxx</replaceable></literal> command 
+      set used in the network layer; in other words: Their values are being
+      increased whenever prepared statements API calls such as 
+      <command>mysql_stmt_prepare()</command>,
+      <command>mysql_stmt_execute()</command>, and so forth are executed.
+      However, <literal>Com_stmt_prepare</literal>, 
+      <literal>Com_stmt_execute</literal> and 
+      <literal>Com_stmt_close</literal> are also increased when one issues 
+      the following SQL statements: <literal>PREPARE</literal>, 
+      <literal>EXECUTE</literal>, or
<literal>DEALLOCATE</literal>
+      respectively.
+      <!--
+      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
+      <literal>DEALLOCATE</literal> statements.
+      -->
+      <literal>Com_stmt_fetch</literal> stands for the total number of
network 
+      round-trips issued when fetching from cursors.
+     </para>
+     <para>
+      All of the
<literal>Com_stmt_<replaceable>xxx</replaceable></literal>
+      variables are increased even if their argument (a prepared statement) is 
+      unknown or an error occurred during execution; in other words: Their 
+      values correspond to the number of requests issued, not to the number of
+      requests successfully completed.
+     </para>
+    </listitem>
 
     <listitem><para>
      <literal>Connections</literal>
@@ -9970,7 +10026,7 @@
     <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
+     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>