Below is the list of changes that have just been committed into a local
mysqldoc repository of paul. When paul 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.3615 05/09/23 14:18:22 paul@stripped +4 -0
Describe prepared statement logging. (WL#1085)
refman/mysql-apis.xml
1.56 05/09/23 14:18:20 paul@stripped +74 -0
Describe prepared statement logging. (WL#1085)
refman-5.1/mysql-apis.xml
1.38 05/09/23 14:18:20 paul@stripped +74 -0
Sync.
refman-5.0/mysql-apis.xml
1.38 05/09/23 14:18:20 paul@stripped +74 -0
Sync.
refman-4.1/mysql-apis.xml
1.53 05/09/23 14:18:20 paul@stripped +74 -0
Sync.
# 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: paul
# Host: kite-hub.kitebird.com
# Root: /src/extern/MySQL/bk/mysqldoc
--- 1.37/refman-5.1/mysql-apis.xml 2005-09-12 14:43:12 -05:00
+++ 1.38/refman-5.1/mysql-apis.xml 2005-09-23 14:18:20 -05:00
@@ -8938,6 +8938,80 @@
<literal>mysql_stmt_sqlstate()</literal>, respectively.
</para>
+ <para>
+ <emphasis role="bold">Prepared Statement Logging</emphasis>
+ </para>
+
+ <para>
+ For prepared statements that are executed with the
+ <literal>mysql_stmt_prepare()</literal> and
+ <literal>mysql_stmt_execute()</literal> C API functions, the
+ server writes <literal>Prepare</literal> and
+ <literal>Execute</literal> lines to the general query log so
+ that you can tell when statements are prepared and executed.
+ </para>
+
+ <para>
+ Suppose that you prepare and execute a statement as follows:
+ </para>
+
+ <orderedlist>
+
+ <listitem>
+ <para>
+ Call <literal>mysql_stmt_prepare()</literal> to prepare the
+ statement string <literal>"SELECT ?"</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Call <literal>mysql_stmt_bind_param()</literal> to bind the
+ value <literal>3</literal> to the parameter in the prepared
+ statement.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Call <literal>mysql_stmt_execute()</literal> to execute the
+ prepared statement.
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+ <para>
+ As a result of the preceding calls, the server writes the
+ following lines to the general query log:
+ </para>
+
+<programlisting>
+Prepare [1] SELECT ?
+Execute [1] SELECT 3
+</programlisting>
+
+ <para>
+ Each <literal>Prepare</literal> and <literal>Execute</literal>
+ line in the log is tagged with a
+ <literal>[<replaceable>n</replaceable>]</literal> statement
+ identifier so that you can keep track of which prepared
+ statement is being logged. <replaceable>n</replaceable> is a
+ positive integer. If there are multiple prepared statements
+ active simultaneously for the client,
+ <replaceable>n</replaceable> may be greater than 1. Each
+ <literal>Execute</literal> lines shows a prepared statement
+ after substitution of data values for <literal>?</literal>
+ parameters.
+ </para>
+
+ <para>
+ Version notes: <literal>Prepare</literal> lines are displayed
+ without <literal>[<replaceable>n</replaceable>]</literal> before
+ MySQL 4.1.10. <literal>Execute</literal> lines are not displayed
+ at all before MySQL 4.1.10.
+ </para>
+
</section>
<section id="c-api-prepared-statement-functions">
--- 1.52/refman-4.1/mysql-apis.xml 2005-09-12 14:43:10 -05:00
+++ 1.53/refman-4.1/mysql-apis.xml 2005-09-23 14:18:20 -05:00
@@ -8895,6 +8895,80 @@
<literal>mysql_stmt_sqlstate()</literal>, respectively.
</para>
+ <para>
+ <emphasis role="bold">Prepared Statement Logging</emphasis>
+ </para>
+
+ <para>
+ For prepared statements that are executed with the
+ <literal>mysql_stmt_prepare()</literal> and
+ <literal>mysql_stmt_execute()</literal> C API functions, the
+ server writes <literal>Prepare</literal> and
+ <literal>Execute</literal> lines to the general query log so
+ that you can tell when statements are prepared and executed.
+ </para>
+
+ <para>
+ Suppose that you prepare and execute a statement as follows:
+ </para>
+
+ <orderedlist>
+
+ <listitem>
+ <para>
+ Call <literal>mysql_stmt_prepare()</literal> to prepare the
+ statement string <literal>"SELECT ?"</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Call <literal>mysql_stmt_bind_param()</literal> to bind the
+ value <literal>3</literal> to the parameter in the prepared
+ statement.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Call <literal>mysql_stmt_execute()</literal> to execute the
+ prepared statement.
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+ <para>
+ As a result of the preceding calls, the server writes the
+ following lines to the general query log:
+ </para>
+
+<programlisting>
+Prepare [1] SELECT ?
+Execute [1] SELECT 3
+</programlisting>
+
+ <para>
+ Each <literal>Prepare</literal> and <literal>Execute</literal>
+ line in the log is tagged with a
+ <literal>[<replaceable>n</replaceable>]</literal> statement
+ identifier so that you can keep track of which prepared
+ statement is being logged. <replaceable>n</replaceable> is a
+ positive integer. If there are multiple prepared statements
+ active simultaneously for the client,
+ <replaceable>n</replaceable> may be greater than 1. Each
+ <literal>Execute</literal> lines shows a prepared statement
+ after substitution of data values for <literal>?</literal>
+ parameters.
+ </para>
+
+ <para>
+ Version notes: <literal>Prepare</literal> lines are displayed
+ without <literal>[<replaceable>n</replaceable>]</literal> before
+ MySQL 4.1.10. <literal>Execute</literal> lines are not displayed
+ at all before MySQL 4.1.10.
+ </para>
+
</section>
<section id="c-api-prepared-statement-functions">
--- 1.55/refman/mysql-apis.xml 2005-09-17 16:16:47 -05:00
+++ 1.56/refman/mysql-apis.xml 2005-09-23 14:18:20 -05:00
@@ -9026,6 +9026,80 @@
<literal>mysql_stmt_sqlstate()</literal>, respectively.
</para>
+ <para>
+ <emphasis role="bold">Prepared Statement Logging</emphasis>
+ </para>
+
+ <para>
+ For prepared statements that are executed with the
+ <literal>mysql_stmt_prepare()</literal> and
+ <literal>mysql_stmt_execute()</literal> C API functions, the
+ server writes <literal>Prepare</literal> and
+ <literal>Execute</literal> lines to the general query log so
+ that you can tell when statements are prepared and executed.
+ </para>
+
+ <para>
+ Suppose that you prepare and execute a statement as follows:
+ </para>
+
+ <orderedlist>
+
+ <listitem>
+ <para>
+ Call <literal>mysql_stmt_prepare()</literal> to prepare the
+ statement string <literal>"SELECT ?"</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Call <literal>mysql_stmt_bind_param()</literal> to bind the
+ value <literal>3</literal> to the parameter in the prepared
+ statement.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Call <literal>mysql_stmt_execute()</literal> to execute the
+ prepared statement.
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+ <para>
+ As a result of the preceding calls, the server writes the
+ following lines to the general query log:
+ </para>
+
+<programlisting>
+Prepare [1] SELECT ?
+Execute [1] SELECT 3
+</programlisting>
+
+ <para>
+ Each <literal>Prepare</literal> and <literal>Execute</literal>
+ line in the log is tagged with a
+ <literal>[<replaceable>n</replaceable>]</literal> statement
+ identifier so that you can keep track of which prepared
+ statement is being logged. <replaceable>n</replaceable> is a
+ positive integer. If there are multiple prepared statements
+ active simultaneously for the client,
+ <replaceable>n</replaceable> may be greater than 1. Each
+ <literal>Execute</literal> lines shows a prepared statement
+ after substitution of data values for <literal>?</literal>
+ parameters.
+ </para>
+
+ <para>
+ Version notes: <literal>Prepare</literal> lines are displayed
+ without <literal>[<replaceable>n</replaceable>]</literal> before
+ MySQL 4.1.10. <literal>Execute</literal> lines are not displayed
+ at all before MySQL 4.1.10.
+ </para>
+
</section>
<section id="c-api-prepared-statement-functions">
--- 1.37/refman-5.0/mysql-apis.xml 2005-09-12 14:43:12 -05:00
+++ 1.38/refman-5.0/mysql-apis.xml 2005-09-23 14:18:20 -05:00
@@ -8932,6 +8932,80 @@
<literal>mysql_stmt_sqlstate()</literal>, respectively.
</para>
+ <para>
+ <emphasis role="bold">Prepared Statement Logging</emphasis>
+ </para>
+
+ <para>
+ For prepared statements that are executed with the
+ <literal>mysql_stmt_prepare()</literal> and
+ <literal>mysql_stmt_execute()</literal> C API functions, the
+ server writes <literal>Prepare</literal> and
+ <literal>Execute</literal> lines to the general query log so
+ that you can tell when statements are prepared and executed.
+ </para>
+
+ <para>
+ Suppose that you prepare and execute a statement as follows:
+ </para>
+
+ <orderedlist>
+
+ <listitem>
+ <para>
+ Call <literal>mysql_stmt_prepare()</literal> to prepare the
+ statement string <literal>"SELECT ?"</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Call <literal>mysql_stmt_bind_param()</literal> to bind the
+ value <literal>3</literal> to the parameter in the prepared
+ statement.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Call <literal>mysql_stmt_execute()</literal> to execute the
+ prepared statement.
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+ <para>
+ As a result of the preceding calls, the server writes the
+ following lines to the general query log:
+ </para>
+
+<programlisting>
+Prepare [1] SELECT ?
+Execute [1] SELECT 3
+</programlisting>
+
+ <para>
+ Each <literal>Prepare</literal> and <literal>Execute</literal>
+ line in the log is tagged with a
+ <literal>[<replaceable>n</replaceable>]</literal> statement
+ identifier so that you can keep track of which prepared
+ statement is being logged. <replaceable>n</replaceable> is a
+ positive integer. If there are multiple prepared statements
+ active simultaneously for the client,
+ <replaceable>n</replaceable> may be greater than 1. Each
+ <literal>Execute</literal> lines shows a prepared statement
+ after substitution of data values for <literal>?</literal>
+ parameters.
+ </para>
+
+ <para>
+ Version notes: <literal>Prepare</literal> lines are displayed
+ without <literal>[<replaceable>n</replaceable>]</literal> before
+ MySQL 4.1.10. <literal>Execute</literal> lines are not displayed
+ at all before MySQL 4.1.10.
+ </para>
+
</section>
<section id="c-api-prepared-statement-functions">
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (paul:1.3615) | paul | 23 Sep |
