MySQL Lists: internals: bk commit - mysqldoc@docsrva tree (stefan:1.3548)

List:	Internals	« Previous Message Next Message »
From:	stefan	Date:	September 13 2005 4:28pm
Subject:	bk commit - mysqldoc@docsrva tree (stefan:1.3548)
View as plain text
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.3548 05/09/13 16:27:57 stefan@stripped +8 -0
  sql-syntax.xml, mysql-database-administration.xml:
    Sync with refman
  sql-syntax.xml:
    Add description of ONE_SHOT, and examples
    (thanks, Guilhem, for providing that information!)
  mysql-database-administration.xml:
    Add ONE_SHOT with reference to description in sql_syntax.xml

  refman-5.1/sql-syntax.xml
    1.40 05/09/13 16:27:40 stefan@stripped +58 -0
    Sync with refman

  refman-5.1/mysql-database-administration.xml
    1.40 05/09/13 16:27:38 stefan@stripped +22 -0
    Sync with refman

  refman-5.0/sql-syntax.xml
    1.42 05/09/13 16:27:36 stefan@stripped +58 -0
    Sync with refman

  refman-5.0/mysql-database-administration.xml
    1.41 05/09/13 16:27:34 stefan@stripped +22 -0
    Sync with refman

  refman-4.1/sql-syntax.xml
    1.59 05/09/13 16:27:32 stefan@stripped +58 -0
    Sync with refman

  refman-4.1/mysql-database-administration.xml
    1.67 05/09/13 16:27:30 stefan@stripped +22 -0
    Sync with refman

  refman/sql-syntax.xml
    1.67 05/09/13 16:26:56 stefan@stripped +58 -0
    Add description of ONE_SHOT, and examples
    (thanks, Guilhem, for providing that information!)

  refman/mysql-database-administration.xml
    1.81 05/09/13 16:26:27 stefan@stripped +11 -0
    Add ONE_SHOT with reference to description in sql_syntax.xml

# 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.39/refman-5.1/mysql-database-administration.xml	2005-09-12 17:18:26 +02:00
+++ 1.40/refman-5.1/mysql-database-administration.xml	2005-09-13 16:27:38 +02:00
@@ -7732,6 +7732,28 @@
 
           <listitem>
             <para>
+              <literal>one_shot</literal>
+            </para>
+            <para>
+              This is not a variable, but it can be used when setting
+              some variables. It's described in
+              <xref linkend="set-option"/>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <literal>one_shot</literal>
+            </para>
+            <para>
+              This is not a variable, but it can be used when setting
+              some variables. It's described in
+              <xref linkend="set-option"/>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
               <literal>open_files_limit</literal>
             </para>
 

--- 1.39/refman-5.1/sql-syntax.xml	2005-09-12 17:18:26 +02:00
+++ 1.40/refman-5.1/sql-syntax.xml	2005-09-13 16:27:40 +02:00
@@ -12893,6 +12893,64 @@
 
         <listitem>
           <para>
+            <literal>ONE_SHOT</literal>
+          </para>
+          <para>
+            This is not a server system variable, but it can be used
+            to influence the effect of variables that set the character
+            set, the collation, and the time zone.
+            <literal>ONE_SHOT</literal> is primarily used for 
+            replication purposes: <command>mysqlbinlog</command> uses 
+            <literal>SET ONE_SHOT</literal> to temporarily modify the 
+            values of character set, collation, and timezone variables 
+            to reflect at rollforward what they were originally.
+            <literal>ONE_SHOT</literal> is available as of MySQL 
+            4.1.3 and 5.0.
+          </para>
+          <para>
+            You cannot use <literal>ONE_SHOT</literal> with other than
+            the allowed set of variables; if you try, you get an error
+            like this:
+<programlisting>
+mysql> <userinput>SET ONE_SHOT max_allowed_packet = 1;</userinput>
+ERROR 1382 (HY000): The 'SET ONE_SHOT' syntax is reserved for purposes internal to the
MySQL server 
+</programlisting>
+          </para>
+          <para>
+            If <literal>ONE_SHOT</literal> is used with the allowed 
+            variables, it changes the variables as requested, but
+            resets, after the next statement, all character set,
+            collation, and time zone-related server system variables.
+            The only exception when resetting doesn't happen is when
+            the next statement is a <literal>SET</literal> statement.
+            In other words, resetting takes place after the next
+            non-<literal>SET</literal> statement. Example:
+<programlisting>
+mysql> <userinput>SET ONE_SHOT character_set_connection =
latin5;</userinput>
+
+mysql> <userinput>SET ONE_SHOT collation_connection =
latin5_turkish_ci;</userinput>
+
+mysql> <userinput>SHOW VARIABLES LIKE '%_connection';</userinput>
++--------------------------+-------------------+
+| Variable_name            | Value             |
++--------------------------+-------------------+
+| character_set_connection | latin5            |
+| collation_connection     | latin5_turkish_ci |
++--------------------------+-------------------+
+
+mysql> <userinput>SHOW VARIABLES LIKE '%_connection';</userinput>
++--------------------------+-------------------+
+| Variable_name            | Value             |
++--------------------------+-------------------+
+| character_set_connection | latin1            |
+| collation_connection     | latin1_swedish_ci |
++--------------------------+-------------------+
+</programlisting>
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
             <literal>SQL_NOTES = {0 | 1}</literal>
           </para>
 

--- 1.66/refman-4.1/mysql-database-administration.xml	2005-09-11 01:16:50 +02:00
+++ 1.67/refman-4.1/mysql-database-administration.xml	2005-09-13 16:27:30 +02:00
@@ -6412,6 +6412,28 @@
 
           <listitem>
             <para>
+              <literal>one_shot</literal>
+            </para>
+            <para>
+              This is not a variable, but it can be used when setting
+              some variables. It's described in
+              <xref linkend="set-option"/>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <literal>one_shot</literal>
+            </para>
+            <para>
+              This is not a variable, but it can be used when setting
+              some variables. It's described in
+              <xref linkend="set-option"/>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
               <literal>open_files_limit</literal>
             </para>
 

--- 1.58/refman-4.1/sql-syntax.xml	2005-09-12 17:18:20 +02:00
+++ 1.59/refman-4.1/sql-syntax.xml	2005-09-13 16:27:32 +02:00
@@ -12562,6 +12562,64 @@
 
         <listitem>
           <para>
+            <literal>ONE_SHOT</literal>
+          </para>
+          <para>
+            This is not a server system variable, but it can be used
+            to influence the effect of variables that set the character
+            set, the collation, and the time zone.
+            <literal>ONE_SHOT</literal> is primarily used for 
+            replication purposes: <command>mysqlbinlog</command> uses 
+            <literal>SET ONE_SHOT</literal> to temporarily modify the 
+            values of character set, collation, and timezone variables 
+            to reflect at rollforward what they were originally.
+            <literal>ONE_SHOT</literal> is available as of MySQL 
+            4.1.3 and 5.0.
+          </para>
+          <para>
+            You cannot use <literal>ONE_SHOT</literal> with other than
+            the allowed set of variables; if you try, you get an error
+            like this:
+<programlisting>
+mysql> <userinput>SET ONE_SHOT max_allowed_packet = 1;</userinput>
+ERROR 1382 (HY000): The 'SET ONE_SHOT' syntax is reserved for purposes internal to the
MySQL server 
+</programlisting>
+          </para>
+          <para>
+            If <literal>ONE_SHOT</literal> is used with the allowed 
+            variables, it changes the variables as requested, but
+            resets, after the next statement, all character set,
+            collation, and time zone-related server system variables.
+            The only exception when resetting doesn't happen is when
+            the next statement is a <literal>SET</literal> statement.
+            In other words, resetting takes place after the next
+            non-<literal>SET</literal> statement. Example:
+<programlisting>
+mysql> <userinput>SET ONE_SHOT character_set_connection =
latin5;</userinput>
+
+mysql> <userinput>SET ONE_SHOT collation_connection =
latin5_turkish_ci;</userinput>
+
+mysql> <userinput>SHOW VARIABLES LIKE '%_connection';</userinput>
++--------------------------+-------------------+
+| Variable_name            | Value             |
++--------------------------+-------------------+
+| character_set_connection | latin5            |
+| collation_connection     | latin5_turkish_ci |
++--------------------------+-------------------+
+
+mysql> <userinput>SHOW VARIABLES LIKE '%_connection';</userinput>
++--------------------------+-------------------+
+| Variable_name            | Value             |
++--------------------------+-------------------+
+| character_set_connection | latin1            |
+| collation_connection     | latin1_swedish_ci |
++--------------------------+-------------------+
+</programlisting>
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
             <literal>SQL_NOTES = {0 | 1}</literal>
           </para>
 

--- 1.80/refman/mysql-database-administration.xml	2005-09-12 17:18:28 +02:00
+++ 1.81/refman/mysql-database-administration.xml	2005-09-13 16:26:27 +02:00
@@ -8050,6 +8050,17 @@
 
           <listitem>
             <para>
+              <literal>one_shot</literal>
+            </para>
+            <para>
+              This is not a variable, but it can be used when setting
+              some variables. It's described in
+              <xref linkend="set-option"/>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
               <literal>open_files_limit</literal>
             </para>
 

--- 1.66/refman/sql-syntax.xml	2005-09-12 17:18:28 +02:00
+++ 1.67/refman/sql-syntax.xml	2005-09-13 16:26:56 +02:00
@@ -12933,6 +12933,64 @@
 
         <listitem>
           <para>
+            <literal>ONE_SHOT</literal>
+          </para>
+          <para>
+            This is not a server system variable, but it can be used
+            to influence the effect of variables that set the character
+            set, the collation, and the time zone.
+            <literal>ONE_SHOT</literal> is primarily used for 
+            replication purposes: <command>mysqlbinlog</command> uses 
+            <literal>SET ONE_SHOT</literal> to temporarily modify the 
+            values of character set, collation, and timezone variables 
+            to reflect at rollforward what they were originally.
+            <literal>ONE_SHOT</literal> is available as of MySQL 
+            4.1.3 and 5.0.
+          </para>
+          <para>
+            You cannot use <literal>ONE_SHOT</literal> with other than
+            the allowed set of variables; if you try, you get an error
+            like this:
+<programlisting>
+mysql> <userinput>SET ONE_SHOT max_allowed_packet = 1;</userinput>
+ERROR 1382 (HY000): The 'SET ONE_SHOT' syntax is reserved for purposes internal to the
MySQL server 
+</programlisting>
+          </para>
+          <para>
+            If <literal>ONE_SHOT</literal> is used with the allowed 
+            variables, it changes the variables as requested, but
+            resets, after the next statement, all character set,
+            collation, and time zone-related server system variables.
+            The only exception when resetting doesn't happen is when
+            the next statement is a <literal>SET</literal> statement.
+            In other words, resetting takes place after the next
+            non-<literal>SET</literal> statement. Example:
+<programlisting>
+mysql> <userinput>SET ONE_SHOT character_set_connection =
latin5;</userinput>
+
+mysql> <userinput>SET ONE_SHOT collation_connection =
latin5_turkish_ci;</userinput>
+
+mysql> <userinput>SHOW VARIABLES LIKE '%_connection';</userinput>
++--------------------------+-------------------+
+| Variable_name            | Value             |
++--------------------------+-------------------+
+| character_set_connection | latin5            |
+| collation_connection     | latin5_turkish_ci |
++--------------------------+-------------------+
+
+mysql> <userinput>SHOW VARIABLES LIKE '%_connection';</userinput>
++--------------------------+-------------------+
+| Variable_name            | Value             |
++--------------------------+-------------------+
+| character_set_connection | latin1            |
+| collation_connection     | latin1_swedish_ci |
++--------------------------+-------------------+
+</programlisting>
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
             <literal>SQL_NOTES = {0 | 1}</literal>
           </para>
 

--- 1.40/refman-5.0/mysql-database-administration.xml	2005-09-12 17:18:21 +02:00
+++ 1.41/refman-5.0/mysql-database-administration.xml	2005-09-13 16:27:34 +02:00
@@ -7740,6 +7740,28 @@
 
           <listitem>
             <para>
+              <literal>one_shot</literal>
+            </para>
+            <para>
+              This is not a variable, but it can be used when setting
+              some variables. It's described in
+              <xref linkend="set-option"/>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <literal>one_shot</literal>
+            </para>
+            <para>
+              This is not a variable, but it can be used when setting
+              some variables. It's described in
+              <xref linkend="set-option"/>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
               <literal>open_files_limit</literal>
             </para>
 

--- 1.41/refman-5.0/sql-syntax.xml	2005-09-12 17:18:23 +02:00
+++ 1.42/refman-5.0/sql-syntax.xml	2005-09-13 16:27:36 +02:00
@@ -12921,6 +12921,64 @@
 
         <listitem>
           <para>
+            <literal>ONE_SHOT</literal>
+          </para>
+          <para>
+            This is not a server system variable, but it can be used
+            to influence the effect of variables that set the character
+            set, the collation, and the time zone.
+            <literal>ONE_SHOT</literal> is primarily used for 
+            replication purposes: <command>mysqlbinlog</command> uses 
+            <literal>SET ONE_SHOT</literal> to temporarily modify the 
+            values of character set, collation, and timezone variables 
+            to reflect at rollforward what they were originally.
+            <literal>ONE_SHOT</literal> is available as of MySQL 
+            4.1.3 and 5.0.
+          </para>
+          <para>
+            You cannot use <literal>ONE_SHOT</literal> with other than
+            the allowed set of variables; if you try, you get an error
+            like this:
+<programlisting>
+mysql> <userinput>SET ONE_SHOT max_allowed_packet = 1;</userinput>
+ERROR 1382 (HY000): The 'SET ONE_SHOT' syntax is reserved for purposes internal to the
MySQL server 
+</programlisting>
+          </para>
+          <para>
+            If <literal>ONE_SHOT</literal> is used with the allowed 
+            variables, it changes the variables as requested, but
+            resets, after the next statement, all character set,
+            collation, and time zone-related server system variables.
+            The only exception when resetting doesn't happen is when
+            the next statement is a <literal>SET</literal> statement.
+            In other words, resetting takes place after the next
+            non-<literal>SET</literal> statement. Example:
+<programlisting>
+mysql> <userinput>SET ONE_SHOT character_set_connection =
latin5;</userinput>
+
+mysql> <userinput>SET ONE_SHOT collation_connection =
latin5_turkish_ci;</userinput>
+
+mysql> <userinput>SHOW VARIABLES LIKE '%_connection';</userinput>
++--------------------------+-------------------+
+| Variable_name            | Value             |
++--------------------------+-------------------+
+| character_set_connection | latin5            |
+| collation_connection     | latin5_turkish_ci |
++--------------------------+-------------------+
+
+mysql> <userinput>SHOW VARIABLES LIKE '%_connection';</userinput>
++--------------------------+-------------------+
+| Variable_name            | Value             |
++--------------------------+-------------------+
+| character_set_connection | latin1            |
+| collation_connection     | latin1_swedish_ci |
++--------------------------+-------------------+
+</programlisting>
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
             <literal>SQL_NOTES = {0 | 1}</literal>
           </para>
Thread
• bk commit - mysqldoc@docsrva tree (stefan:1.3548)	stefan	13 Sep