MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:paul.dubois Date:February 15 2009 4:18am
Subject:svn commit - mysqldoc@docsrva: r13768 - in trunk: . dynamic-docs/changelog refman-4.1 refman-5.0 refman-5.1 refman-5.1-maria refman-6.0
View as plain text  
Author: paul
Date: 2009-02-15 05:18:11 +0100 (Sun, 15 Feb 2009)
New Revision: 13768

Log:
 r36507@arctic:  paul | 2009-02-14 22:20:57 -0600
 Reformat


Modified:
   trunk/dynamic-docs/changelog/mysqld-1.xml
   trunk/dynamic-docs/changelog/mysqld.xml
   trunk/refman-4.1/backup.xml
   trunk/refman-4.1/dba-log-files.xml
   trunk/refman-4.1/dba-mysqld-server-core.xml
   trunk/refman-4.1/dba-security-core.xml
   trunk/refman-4.1/extending-mysql.xml
   trunk/refman-4.1/installing.xml
   trunk/refman-4.1/internationalization.xml
   trunk/refman-4.1/news-3.23.xml
   trunk/refman-4.1/news-4.0.xml
   trunk/refman-4.1/optimization.xml
   trunk/refman-4.1/programs-client.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:41755
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:38599
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:36506
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:41755
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:38599
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:36507


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2009-02-15 04:17:57 UTC (rev 13767)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2009-02-15 04:18:11 UTC (rev 13768)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 3; 946 bytes

@@ -34321,8 +34321,8 @@
 
       <para>
         <literal>MyISAM</literal> recovery enabled with the
-        <option role="mysqld">--myisam-recover</option> option did not work for
-        partitioned <literal>MyISAM</literal> tables.
+        <option role="mysqld">--myisam-recover</option> option did not
+        work for partitioned <literal>MyISAM</literal> tables.
       </para>
 
     </message>

@@ -38051,7 +38051,8 @@
     <message>
 
       <para>
-        The deprecated <option role="mysqld">--default-table-type</option> server
+        The deprecated
+        <option role="mysqld">--default-table-type</option> server
         option has been removed.
       </para>
 


Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml	2009-02-15 04:17:57 UTC (rev 13767)
+++ trunk/dynamic-docs/changelog/mysqld.xml	2009-02-15 04:18:11 UTC (rev 13768)
Changed blocks: 23, Lines Added: 73, Lines Deleted: 69; 12090 bytes

@@ -12348,9 +12348,9 @@
     <message>
 
       <para>
-        Removed a misleading "check permissions on
-        master.info" from a replication error message, because the
-        cause of the problem could be different from permissions.
+        Removed a misleading "check permissions on master.info" from a
+        replication error message, because the cause of the problem
+        could be different from permissions.
       </para>
 
     </message>

@@ -27833,11 +27833,11 @@
     <message>
 
       <para>
-        The <option role="mysqld">--memlock</option> option relies on system calls
-        that are unreliable on some operating systems. If a crash
-        occurs, the server now checks whether <option role="mysqld">--memlock</option>
-        was specified and if so issues some information about possible
-        workarounds.
+        The <option role="mysqld">--memlock</option> option relies on
+        system calls that are unreliable on some operating systems. If a
+        crash occurs, the server now checks whether
+        <option role="mysqld">--memlock</option> was specified and if so
+        issues some information about possible workarounds.
       </para>
 
     </message>

@@ -28190,11 +28190,11 @@
     <message>
 
       <para>
-        A spurious "duplicate key" error resulted from
-        executing a <literal role="stmt">REPLACE</literal> or
-        <literal>INSERT ... ON DUPLICATE KEY UPDATE</literal> statement
-        performing a multiple-row insert on a table having unique and
-        full-text indexes.
+        A spurious "duplicate key" error resulted from executing a
+        <literal role="stmt">REPLACE</literal> or <literal>INSERT ... ON
+        DUPLICATE KEY UPDATE</literal> statement performing a
+        multiple-row insert on a table having unique and full-text
+        indexes.
       </para>
 
     </message>

@@ -33811,8 +33811,7 @@
       <para>
         A missing <function>DBUG_RETURN()</function> caused the server
         to emit a spurious error message: <literal>missing DBUG_RETURN
-        or DBUG_VOID_RETURN macro in function
-        "open_table"</literal>.
+        or DBUG_VOID_RETURN macro in function "open_table"</literal>.
       </para>
 
     </message>

@@ -35741,8 +35740,10 @@
     <message>
 
       <para>
-        Added the <option role="mysqld">--default-storage-engine</option> server
-        option as a synonym for <option role="mysqld">--default-table-type</option>.
+        Added the
+        <option role="mysqld">--default-storage-engine</option> server
+        option as a synonym for
+        <option role="mysqld">--default-table-type</option>.
       </para>
 
     </message>

@@ -36843,9 +36844,8 @@
     <message>
 
       <para>
-        Comparisons like <literal>SELECT "A\\" LIKE
-        "A\\";</literal> fail when using <literal>SET NAMES
-        utf8;</literal>.
+        Comparisons like <literal>SELECT "A\\" LIKE "A\\";</literal>
+        fail when using <literal>SET NAMES utf8;</literal>.
       </para>
 
     </message>

@@ -39311,10 +39311,12 @@
     <message>
 
       <para>
-        The <option role="mysqld">--collation-server</option> server option was being
-        ignored. With the fix, if you choose a non-default character set
-        with <option role="mysqld">--character-set-server</option>, you should also
-        use <option role="mysqld">--collation-server</option> to specify the
+        The <option role="mysqld">--collation-server</option> server
+        option was being ignored. With the fix, if you choose a
+        non-default character set with
+        <option role="mysqld">--character-set-server</option>, you
+        should also use
+        <option role="mysqld">--collation-server</option> to specify the
         collation.
       </para>
 

@@ -49931,8 +49933,8 @@
 
       <para>
         The result of executing of a prepared statement created with
-        <literal>PREPARE s FROM "SELECT 1 LIMIT ?"</literal>
-        was not replicated correctly.
+        <literal>PREPARE s FROM "SELECT 1 LIMIT ?"</literal> was not
+        replicated correctly.
       </para>
 
     </message>

@@ -68805,8 +68807,8 @@
         <literal>DEFINER</literal>, <literal>SQL SECURITY
         DEFINER</literal> and <literal>WITH CHECK OPTION</literal>
         clauses of a <literal role="stmt">CREATE VIEW</literal>
-        statement with "not in version" comments to prevent
-        errors in earlier versions of MySQL.
+        statement with "not in version" comments to prevent errors in
+        earlier versions of MySQL.
       </para>
 
     </message>

@@ -75053,8 +75055,8 @@
     <message>
 
       <para>
-        The <option role="mysqld">--default-storage-engine</option> server option did
-        not work.
+        The <option role="mysqld">--default-storage-engine</option>
+        server option did not work.
       </para>
 
     </message>

@@ -84265,11 +84267,11 @@
       <para>
         Using <option>--with-debug</option> to configure MySQL with
         debugging support enables you to use the
-        <option>--debug="d,parser_debug"</option> option when
-        you start the server. This causes the Bison parser that is used
-        to process SQL statements to dump a parser trace to the server's
-        standard error output. Typically, this output is written to the
-        error log.
+        <option>--debug="d,parser_debug"</option> option when you start
+        the server. This causes the Bison parser that is used to process
+        SQL statements to dump a parser trace to the server's standard
+        error output. Typically, this output is written to the error
+        log.
       </para>
 
     </message>

@@ -86345,9 +86347,9 @@
     <message>
 
       <para>
-        Added the <option role="mysqld">--secure-file-priv</option> option for
-        <command>mysqld</command>, which limits the effect of the
-        <literal role="func">LOAD_FILE()</literal> function and the
+        Added the <option role="mysqld">--secure-file-priv</option>
+        option for <command>mysqld</command>, which limits the effect of
+        the <literal role="func">LOAD_FILE()</literal> function and the
         <literal role="stmt">LOAD DATA</literal> and
         <literal role="stmt" condition="select">SELECT ... INTO
         OUTFILE</literal> statements to work only with files in a given

@@ -99245,10 +99247,10 @@
     <message>
 
       <para>
-        Added the <option role="mysqld">--port-open-timeout</option> option to
-        <command>mysqld</command> to control how many seconds the server
-        should wait for the TCP/IP port to become free if it cannot be
-        opened.
+        Added the <option role="mysqld">--port-open-timeout</option>
+        option to <command>mysqld</command> to control how many seconds
+        the server should wait for the TCP/IP port to become free if it
+        cannot be opened.
       </para>
 
     </message>

@@ -100825,9 +100827,10 @@
     <message>
 
       <para>
-        Added <option role="mysqld">--sql-mode=NO_AUTO_VALUE_ON_ZERO</option> option
-        to suppress the usual behavior of generating the next sequence
-        number when zero is stored in an
+        Added
+        <option role="mysqld">--sql-mode=NO_AUTO_VALUE_ON_ZERO</option>
+        option to suppress the usual behavior of generating the next
+        sequence number when zero is stored in an
         <literal>AUTO_INCREMENT</literal> column. With this mode
         enabled, zero is stored as zero; only storing
         <literal>NULL</literal> generates a sequence number.

@@ -101425,8 +101428,8 @@
 
       <para>
         <command>perror</command> was printing a spurious extra line of
-        output ("Error code ###: Unknown error ###" printed
-        directly before the correct line with the error message).
+        output ("Error code ###: Unknown error ###" printed directly
+        before the correct line with the error message).
       </para>
 
     </message>

@@ -106231,9 +106234,8 @@
 
       <para>
         The binary log file and binary log index file now behave like
-        <literal>MyISAM</literal> when there is a "disk full"
-        or "quota exceeded" error. See
-        <xref linkend="full-disk"/>.
+        <literal>MyISAM</literal> when there is a "disk full" or "quota
+        exceeded" error. See <xref linkend="full-disk"/>.
       </para>
 
     </message>

@@ -109414,8 +109416,8 @@
 
       <para>
         From the Windows distribution, predefined accounts without
-        passwords for remote users ("root@%", "@%")
-        were removed (other distributions never had them).
+        passwords for remote users ("root@%", "@%") were removed (other
+        distributions never had them).
       </para>
 
     </message>

@@ -111915,8 +111917,8 @@
         Performing <literal>INSERT ... SELECT ... JOIN ...
         USING</literal> without qualifying the column names caused
         <literal>ERROR 1052 "column 'x' in field list is
-        ambiguous"</literal> even in cases where the column
-        references were unambiguous.
+        ambiguous"</literal> even in cases where the column references
+        were unambiguous.
       </para>
 
     </message>

@@ -113069,10 +113071,11 @@
       <para>
         This SQL mode also can be enabled automatically when the server
         starts by using the command-line option
-        <option role="mysqld">--sql-mode=NO_BACKSLASH_ESCAPES</option> or by setting
-        <literal>sql-mode=NO_BACKSLASH_ESCAPES</literal> in the server
-        option file (for example, <filename>my.cnf</filename> or
-        <filename>my.ini</filename>, depending on your system).
+        <option role="mysqld">--sql-mode=NO_BACKSLASH_ESCAPES</option>
+        or by setting <literal>sql-mode=NO_BACKSLASH_ESCAPES</literal>
+        in the server option file (for example,
+        <filename>my.cnf</filename> or <filename>my.ini</filename>,
+        depending on your system).
       </para>
 
     </message>

@@ -117256,8 +117259,9 @@
     <message>
 
       <para>
-        Use of <option role="mysqld">--default-storage-engine=innodb</option> resulted
-        in an error with the server reporting that
+        Use of
+        <option role="mysqld">--default-storage-engine=innodb</option>
+        resulted in an error with the server reporting that
         <literal>InnoDB</literal> was an unknown table type.
       </para>
 

@@ -119476,9 +119480,9 @@
       <para>
         Starting <command>mysqld</command> with the
         <option role="mysqld">--skip-innodb</option> and
-        <option role="mysqld">--default-storage-engine=innodb</option> (or
-        <option role="mysqld">--default-table-type=innodb</option> caused a server
-        crash.
+        <option role="mysqld">--default-storage-engine=innodb</option>
+        (or <option role="mysqld">--default-table-type=innodb</option>
+        caused a server crash.
       </para>
 
     </message>

@@ -130130,9 +130134,9 @@
         <literal>mysqldump</literal> could crash or exhibit incorrect
         behavior when some options were given very long values, such as
         <option>--fields-terminated-by="<replaceable>some very long
-        string</replaceable>"</option>. The code has been cleaned
-        up to remove a number of fixed-sized buffers and to be more
-        careful about error conditions in memory allocation.
+        string</replaceable>"</option>. The code has been cleaned up to
+        remove a number of fixed-sized buffers and to be more careful
+        about error conditions in memory allocation.
       </para>
 
     </message>

@@ -130991,9 +130995,9 @@
     <message>
 
       <para>
-        A connection doing a rollback now displays "Rolling
-        back" in the <literal>State</literal> column of
-        <literal role="stmt">SHOW PROCESSLIST</literal>.
+        A connection doing a rollback now displays "Rolling back" in the
+        <literal>State</literal> column of <literal role="stmt">SHOW
+        PROCESSLIST</literal>.
       </para>
 
     </message>


Modified: trunk/refman-4.1/backup.xml
===================================================================
--- trunk/refman-4.1/backup.xml	2009-02-15 04:17:57 UTC (rev 13767)
+++ trunk/refman-4.1/backup.xml	2009-02-15 04:18:11 UTC (rev 13768)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 5; 1387 bytes

@@ -2920,11 +2920,12 @@
         that could have been affected. (These are
         <quote>expected</quote> crashed tables.) To check
         <literal>MyISAM</literal> tables automatically, start the server
-        with the <option role="mysqld">--myisam-recover</option> option, available as
-        of MySQL 3.23.25. If your server is too old to support this
-        option, you could add a test to <command>mysqld_safe</command>
-        that runs <command>myisamchk</command> to check all tables that
-        have been modified during the last 24 hours if there is an old
+        with the <option role="mysqld">--myisam-recover</option> option,
+        available as of MySQL 3.23.25. If your server is too old to
+        support this option, you could add a test to
+        <command>mysqld_safe</command> that runs
+        <command>myisamchk</command> to check all tables that have been
+        modified during the last 24 hours if there is an old
         <filename>.pid</filename> (process ID) file left after a
         restart. (The <filename>.pid</filename> file is created by
         <command>mysqld</command> when it starts and removed when it


Modified: trunk/refman-4.1/dba-log-files.xml
===================================================================
--- trunk/refman-4.1/dba-log-files.xml	2009-02-15 04:17:57 UTC (rev 13767)
+++ trunk/refman-4.1/dba-log-files.xml	2009-02-15 04:18:11 UTC (rev 13768)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 561 bytes

@@ -194,8 +194,8 @@
 
     <remark role="note">
       This instance of "safe_mysql" should not be changed to
-      "mysqld_safe" because it is in the context of a
-      3.23.x-specific command.
+      "mysqld_safe" because it is in the context of a 3.23.x-specific
+      command.
     </remark>
 
     <para>


Modified: trunk/refman-4.1/dba-mysqld-server-core.xml
===================================================================
--- trunk/refman-4.1/dba-mysqld-server-core.xml	2009-02-15 04:17:57 UTC (rev 13767)
+++ trunk/refman-4.1/dba-mysqld-server-core.xml	2009-02-15 04:18:11 UTC (rev 13768)
Changed blocks: 16, Lines Added: 48, Lines Deleted: 46; 9870 bytes

@@ -427,9 +427,9 @@
           Don't ignore character set information sent by the client. To
           ignore client information and use the default server character
           set, use
-          <option role="mysqld" condition="character-set-client-handshake">--skip-character-set-client-handshake</option>; this
-          makes MySQL 4.1 and higher behave like MySQL 4.0. This option
-          was added in MySQL 4.1.15.
+          <option role="mysqld" condition="character-set-client-handshake">--skip-character-set-client-handshake</option>;
+          this makes MySQL 4.1 and higher behave like MySQL 4.0. This
+          option was added in MySQL 4.1.15.
         </para>
       </listitem>
 

@@ -454,8 +454,9 @@
           server character set. See
           <xref linkend="charset-configuration"/>. If you use this
           option to specify a non-default character set, you should also
-          use <option role="mysqld">--collation-server</option> to specify the
-          collation. This option is available as of MySQL 4.1.3.
+          use <option role="mysqld">--collation-server</option> to
+          specify the collation. This option is available as of MySQL
+          4.1.3.
         </para>
       </listitem>
 

@@ -629,8 +630,8 @@
         <para>
           Use <replaceable>charset_name</replaceable> as the default
           character set. This option is deprecated in favor of
-          <option role="mysqld">--character-set-server</option> as of MySQL 4.1.3. See
-          <xref linkend="charset-configuration"/>.
+          <option role="mysqld">--character-set-server</option> as of
+          MySQL 4.1.3. See <xref linkend="charset-configuration"/>.
         </para>
       </listitem>
 

@@ -652,8 +653,8 @@
         <para>
           Use <replaceable>collation_name</replaceable> as the default
           collation. This option is deprecated in favor of
-          <option role="mysqld">--collation-server</option> as of MySQL 4.1.3. See
-          <xref linkend="charset-configuration"/>.
+          <option role="mysqld">--collation-server</option> as of MySQL
+          4.1.3. See <xref linkend="charset-configuration"/>.
         </para>
       </listitem>
 

@@ -674,8 +675,8 @@
 
         <para>
           This option is a synonym for
-          <option role="mysqld">--default-table-type</option>. It is available as of
-          MySQL 4.1.2.
+          <option role="mysqld">--default-table-type</option>. It is
+          available as of MySQL 4.1.2.
         </para>
       </listitem>
 

@@ -1384,11 +1385,11 @@
         </para>
 
         <para>
-          <option role="mysqld">--memlock</option> works on systems that support the
-          <literal>mlockall()</literal> system call; this includes
-          Solaris as well as most Linux distributions that use a 2.4 or
-          newer kernel. On Linux systems, you can tell whether or not
-          <literal>mlockall()</literal> (and thus this option) is
+          <option role="mysqld">--memlock</option> works on systems that
+          support the <literal>mlockall()</literal> system call; this
+          includes Solaris as well as most Linux distributions that use
+          a 2.4 or newer kernel. On Linux systems, you can tell whether
+          or not <literal>mlockall()</literal> (and thus this option) is
           supported by checking to see whether or not it is defined in
           the system <filename>mman.h</filename> file, like this:
 

@@ -1445,12 +1446,12 @@
           <literal>DEFAULT</literal>, <literal>BACKUP</literal>,
           <literal>FORCE</literal>, or <literal>QUICK</literal>. If you
           specify multiple values, separate them by commas. You can also
-          use a value of <literal>""</literal> to disable this
-          option. If this option is used, each time
-          <command>mysqld</command> opens a <literal>MyISAM</literal>
-          table, it checks whether the table is marked as crashed or
-          wasn't closed properly. (The last option works only if you are
-          running with external locking disabled.) If this is the case,
+          use a value of <literal>""</literal> to disable this option.
+          If this option is used, each time <command>mysqld</command>
+          opens a <literal>MyISAM</literal> table, it checks whether the
+          table is marked as crashed or wasn't closed properly. (The
+          last option works only if you are running with external
+          locking disabled.) If this is the case,
           <command>mysqld</command> runs a check on the table. If the
           table was corrupted, <command>mysqld</command> attempts to
           repair it.

@@ -3752,8 +3753,8 @@
           writes on keys a lot, but if you use this feature, you should
           add automatic checking of all <literal>MyISAM</literal> tables
           by starting the server with the
-          <option role="mysqld">--myisam-recover</option> option (for example,
-          <option>--myisam-recover=BACKUP,FORCE</option>). See
+          <option role="mysqld">--myisam-recover</option> option (for
+          example, <option>--myisam-recover=BACKUP,FORCE</option>). See
           <xref linkend="server-options"/>, and
           <xref linkend="myisam-start"/>.
         </para>

@@ -3936,8 +3937,8 @@
 
         <para>
           The default variable value is
-          <literal>'+&nbsp;-&gt;&lt;()~*:""&amp;|'</literal>.
-          The rules for changing the value are as follows:
+          <literal>'+&nbsp;-&gt;&lt;()~*:""&amp;|'</literal>. The rules
+          for changing the value are as follows:
         </para>
 
         <itemizedlist>

@@ -4954,8 +4955,8 @@
 
         <para>
           Whether <command>mysqld</command> was locked in memory with
-          <option role="mysqld">--memlock</option>. This variable was added in MySQL
-          3.23.25.
+          <option role="mysqld">--memlock</option>. This variable was
+          added in MySQL 3.23.25.
         </para>
       </listitem>
 

@@ -5814,7 +5815,8 @@
         </para>
 
         <para>
-          The value of the <option role="mysqld">--myisam-recover</option> option. See
+          The value of the
+          <option role="mysqld">--myisam-recover</option> option. See
           <xref linkend="server-options"/>. This variable was added in
           MySQL 3.23.36.
         </para>

@@ -6681,10 +6683,11 @@
 
         <para>
           If the MySQL server has been started with the
-          <option role="mysqld">--secure-auth</option> option, it blocks connections
-          from all accounts that have passwords stored in the old
-          (pre-4.1) format. In that case, the value of this variable is
-          <literal>ON</literal>, otherwise it is <literal>OFF</literal>.
+          <option role="mysqld">--secure-auth</option> option, it blocks
+          connections from all accounts that have passwords stored in
+          the old (pre-4.1) format. In that case, the value of this
+          variable is <literal>ON</literal>, otherwise it is
+          <literal>OFF</literal>.
         </para>
 
         <para>

@@ -7139,8 +7142,8 @@
         <para>
           The default table type (storage engine). To set the table type
           at server startup, use the
-          <option role="mysqld">--default-table-type</option> option. This variable
-          was added in MySQL 3.23.0. See
+          <option role="mysqld">--default-table-type</option> option.
+          This variable was added in MySQL 3.23.0. See
           <xref linkend="server-options"/>.
         </para>
       </listitem>

@@ -7280,9 +7283,9 @@
           means, <quote>use the value of
           <literal role="sysvar">system_time_zone</literal></quote>).
           The value can be specified explicitly at server startup with
-          the <option role="mysqld">--default-time-zone</option> option. See
-          <xref linkend="time-zone-support"/>. This variable was added
-          in MySQL 4.1.3.
+          the <option role="mysqld">--default-time-zone</option> option.
+          See <xref linkend="time-zone-support"/>. This variable was
+          added in MySQL 4.1.3.
         </para>
       </listitem>
 

@@ -10357,8 +10360,8 @@
       separated by comma (<quote><literal>,</literal></quote>)
       characters. The default value is empty (no modes set). The
       <replaceable>modes</replaceable> value also can be empty
-      (<option role="mysqld">--sql-mode=""</option> on the command line, or
-      <option role="mysqld">sql-mode=""</option> in
+      (<option role="mysqld">--sql-mode=""</option> on the command line,
+      or <option role="mysqld">sql-mode=""</option> in
       <filename>my.cnf</filename> on Unix systems or in
       <filename>my.ini</filename> on Windows) if you want to clear it
       explicitly.

@@ -10414,12 +10417,11 @@
         </para>
 
         <para>
-          Treat <quote><literal>"</literal></quote> as an
-          identifier quote character (like the
-          <quote><literal>`</literal></quote> quote character) and not
-          as a string quote character. You can still use
-          <quote><literal>`</literal></quote> to quote identifiers with
-          this mode enabled. With
+          Treat <quote><literal>"</literal></quote> as an identifier
+          quote character (like the <quote><literal>`</literal></quote>
+          quote character) and not as a string quote character. You can
+          still use <quote><literal>`</literal></quote> to quote
+          identifiers with this mode enabled. With
           <literal role="sqlmode">ANSI_QUOTES</literal> enabled, you
           cannot use double quotes to quote literal strings, because it
           is interpreted as an identifier. (Added in MySQL 4.0.0)


Modified: trunk/refman-4.1/dba-security-core.xml
===================================================================
--- trunk/refman-4.1/dba-security-core.xml	2009-02-15 04:17:57 UTC (rev 13767)
+++ trunk/refman-4.1/dba-security-core.xml	2009-02-15 04:18:11 UTC (rev 13768)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 818 bytes

@@ -234,9 +234,9 @@
             <para>
               Try to enter single and double quote marks
               (<quote><literal>'</literal></quote> and
-              <quote><literal>"</literal></quote>) in all of your
-              Web forms. If you get any kind of MySQL error, investigate
-              the problem right away.
+              <quote><literal>"</literal></quote>) in all of your Web
+              forms. If you get any kind of MySQL error, investigate the
+              problem right away.
             </para>
           </listitem>
 


Modified: trunk/refman-4.1/extending-mysql.xml
===================================================================
--- trunk/refman-4.1/extending-mysql.xml	2009-02-15 04:17:57 UTC (rev 13767)
+++ trunk/refman-4.1/extending-mysql.xml	2009-02-15 04:18:11 UTC (rev 13768)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 824 bytes

@@ -2459,8 +2459,8 @@
           However, running with <literal>SAFEMALLOC</literal> is quite
           slow, so if you get performance problems you should start
           <command>mysqld</command> with the
-          <option role="mysqld">--skip-safemalloc</option> option. This disables the
-          memory overrun checks for each call to
+          <option role="mysqld">--skip-safemalloc</option> option. This
+          disables the memory overrun checks for each call to
           <literal>malloc()</literal> and <literal>free()</literal>.
         </para>
 


Modified: trunk/refman-4.1/installing.xml
===================================================================
--- trunk/refman-4.1/installing.xml	2009-02-15 04:17:57 UTC (rev 13767)
+++ trunk/refman-4.1/installing.xml	2009-02-15 04:18:11 UTC (rev 13768)
Changed blocks: 4, Lines Added: 14, Lines Deleted: 11; 2941 bytes

@@ -4658,10 +4658,11 @@
 
       <para>
         The last option is to start <command>mysqld</command> with the
-        <option role="mysqld">--standalone</option> and <option>--debug</option>
-        options. In this case, <command>mysqld</command> writes a log
-        file <filename>C:\mysqld.trace</filename> that should contain
-        the reason why <command>mysqld</command> doesn't start. See
+        <option role="mysqld">--standalone</option> and
+        <option>--debug</option> options. In this case,
+        <command>mysqld</command> writes a log file
+        <filename>C:\mysqld.trace</filename> that should contain the
+        reason why <command>mysqld</command> doesn't start. See
         <ulink url="http://forge.mysql.com/wiki/MySQL_Internals_Porting">MySQL
         Internals: Porting</ulink>.
       </para>

@@ -15563,8 +15564,8 @@
           To get a core dump on Linux if <command>mysqld</command> dies
           with a <literal>SIGSEGV</literal> signal, you can start
           <command>mysqld</command> with the
-          <option role="mysqld">--core-file</option> option. Note that you also
-          probably need to raise the core file size by adding
+          <option role="mysqld">--core-file</option> option. Note that
+          you also probably need to raise the core file size by adding
           <command>ulimit -c 1000000</command> to
           <command>mysqld_safe</command> or starting
           <command>mysqld_safe</command> with

@@ -15904,7 +15905,8 @@
           <listitem>
             <para>
               If you have problems with performance under heavy load,
-              try using the <option role="mysqld">--skip-thread-priority</option>
+              try using the
+              <option role="mysqld">--skip-thread-priority</option>
               option to <command>mysqld</command>. This runs all threads
               with the same priority. On Mac OS X, this gives better
               performance, at least until Apple fixes its thread

@@ -16883,10 +16885,11 @@
 
         <para>
           If you have problems with performance under heavy load, try
-          using the <option role="mysqld">--skip-thread-priority</option> option to
-          <command>mysqld</command>. This runs all threads with the same
-          priority. On BSDI 3.1, this gives better performance, at least
-          until BSDI fixes its thread scheduler.
+          using the
+          <option role="mysqld">--skip-thread-priority</option> option
+          to <command>mysqld</command>. This runs all threads with the
+          same priority. On BSDI 3.1, this gives better performance, at
+          least until BSDI fixes its thread scheduler.
         </para>
 
         <para>


Modified: trunk/refman-4.1/internationalization.xml
===================================================================
--- trunk/refman-4.1/internationalization.xml	2009-02-15 04:17:57 UTC (rev 13767)
+++ trunk/refman-4.1/internationalization.xml	2009-02-15 04:18:11 UTC (rev 13768)
Changed blocks: 6, Lines Added: 29, Lines Deleted: 23; 5335 bytes

@@ -516,18 +516,20 @@
           Initially, the server character set and collation depend on
           the options that you use when you start
           <command>mysqld</command>. You can use
-          <option role="mysqld">--character-set-server</option> for the character set.
-          Along with it, you can add <option role="mysqld">--collation-server</option>
-          for the collation. If you don't specify a character set, that
-          is the same as saying
-          <option role="mysqld">--character-set-server=latin1</option>. If you specify
-          only a character set (for example, <literal>latin1</literal>)
-          but not a collation, that is the same as saying
+          <option role="mysqld">--character-set-server</option> for the
+          character set. Along with it, you can add
+          <option role="mysqld">--collation-server</option> for the
+          collation. If you don't specify a character set, that is the
+          same as saying
+          <option role="mysqld">--character-set-server=latin1</option>.
+          If you specify only a character set (for example,
+          <literal>latin1</literal>) but not a collation, that is the
+          same as saying
           <option role="mysqld">--character-set-server=latin1</option>
-          <option role="mysqld">--collation-server=latin1_swedish_ci</option> because
-          <literal>latin1_swedish_ci</literal> is the default collation
-          for <literal>latin1</literal>. Therefore, the following three
-          commands all have the same effect:
+          <option role="mysqld">--collation-server=latin1_swedish_ci</option>
+          because <literal>latin1_swedish_ci</literal> is the default
+          collation for <literal>latin1</literal>. Therefore, the
+          following three commands all have the same effect:
         </para>
 
 <programlisting>

@@ -1683,9 +1685,11 @@
       <para>
         <emphasis role="bold">Specify character settings at server
         startup.</emphasis> To select a character set and collation at
-        server startup, use the <option role="mysqld">--character-set-server</option>
-        and <option role="mysqld">--collation-server</option> options. For example, to
-        specify the options in an option file, include these lines:
+        server startup, use the
+        <option role="mysqld">--character-set-server</option> and
+        <option role="mysqld">--collation-server</option> options. For
+        example, to specify the options in an option file, include these
+        lines:
       </para>
 
 <programlisting>

@@ -1730,10 +1734,10 @@
         <literal>utf8_general_ci</literal> as the default for databases
         and tables and for client connections. It is unnecessary to use
         <option role="mysqld">--character-set-server</option> and
-        <option role="mysqld">--collation-server</option> at server startup. It is
-        also unnecessary for applications to configure their connection
-        using <literal>SET NAMES</literal> or equivalent after they
-        connect to the server.
+        <option role="mysqld">--collation-server</option> at server
+        startup. It is also unnecessary for applications to configure
+        their connection using <literal>SET NAMES</literal> or
+        equivalent after they connect to the server.
       </para>
 
       <para>

@@ -5773,7 +5777,8 @@
             Users of any Japanese character sets should be aware that
             using
             <option role="mysqld">--character-set-client-handshake</option>
-            (or <option role="mysqld" condition="character-set-client-handshake">--skip-character-set-client-handshake</option>)
+            (or
+            <option role="mysqld" condition="character-set-client-handshake">--skip-character-set-client-handshake</option>)
             has an important effect. See
             <xref linkend="server-options"/>.
           </para>

@@ -5831,9 +5836,9 @@
     <para>
       You can change the default server character set and collation with
       the <option role="mysqld">--character-set-server</option> and
-      <option role="mysqld">--collation-server</option> options when you start the
-      server. The collation must be a legal collation for the default
-      character set. (Use the <literal role="stmt">SHOW
+      <option role="mysqld">--collation-server</option> options when you
+      start the server. The collation must be a legal collation for the
+      default character set. (Use the <literal role="stmt">SHOW
       COLLATION</literal> statement to determine which collations are
       available for each character set.) See
       <xref linkend="server-options"/>. Before MySQL 4.1.3, use

@@ -5968,7 +5973,8 @@
         start the server with the <literal>latin1_german1_ci</literal>
         collation, use the
         <option role="mysqld">--character-set-server=latin1</option> and
-        <option role="mysqld">--collation-server=latin1_german1_ci</option> options.
+        <option role="mysqld">--collation-server=latin1_german1_ci</option>
+        options.
       </para>
 
       <para>


Modified: trunk/refman-4.1/news-3.23.xml
===================================================================
--- trunk/refman-4.1/news-3.23.xml	2009-02-15 04:17:57 UTC (rev 13767)
+++ trunk/refman-4.1/news-3.23.xml	2009-02-15 04:18:11 UTC (rev 13768)
Changed blocks: 7, Lines Added: 16, Lines Deleted: 14; 2811 bytes

@@ -737,9 +737,9 @@
           <xref linkend="news-3-23-54"/>) is reverted. Unfortunately,
           there is no way to make it to work, without introducing
           backward-incompatible changes in <filename>my.cnf</filename>.
-          Those who need <option role="mysqld">--chroot</option> functionality, should
-          upgrade to MySQL 4.0. (The fix in the 4.0 branch did not break
-          backward-compatibility).
+          Those who need <option role="mysqld">--chroot</option>
+          functionality, should upgrade to MySQL 4.0. (The fix in the
+          4.0 branch did not break backward-compatibility).
         </para>
       </listitem>
 

@@ -833,8 +833,9 @@
 
       <listitem>
         <para>
-          Fixed bug that prevented <option role="mysqld">--chroot</option>
-          command-line option of <command>mysqld</command> from working.
+          Fixed bug that prevented
+          <option role="mysqld">--chroot</option> command-line option of
+          <command>mysqld</command> from working.
         </para>
       </listitem>
 

@@ -912,8 +913,8 @@
 
       <listitem>
         <para>
-          Fixed that <option role="mysqld">--core-file</option> works on Linux (at
-          least on kernel 2.4.18).
+          Fixed that <option role="mysqld">--core-file</option> works on
+          Linux (at least on kernel 2.4.18).
         </para>
       </listitem>
 

@@ -2048,7 +2049,8 @@
 
       <listitem>
         <para>
-          <option role="mysqld">--core-file</option> now works on Solaris.
+          <option role="mysqld">--core-file</option> now works on
+          Solaris.
         </para>
       </listitem>
 

@@ -2996,8 +2998,8 @@
 
       <listitem>
         <para>
-          Added <option role="mysqld">--skip-stack-trace</option> option to
-          <command>mysqld</command>.
+          Added <option role="mysqld">--skip-stack-trace</option> option
+          to <command>mysqld</command>.
         </para>
       </listitem>
 

@@ -3280,8 +3282,8 @@
 
       <listitem>
         <para>
-          Added <option role="mysqld">--skip-safemalloc</option> option to
-          <command>mysqld</command>.
+          Added <option role="mysqld">--skip-safemalloc</option> option
+          to <command>mysqld</command>.
         </para>
       </listitem>
 

@@ -8930,8 +8932,8 @@
 
       <listitem>
         <para>
-          Added <option role="mysqld">--default-table-type</option> option to
-          <command>mysqld</command>.
+          Added <option role="mysqld">--default-table-type</option>
+          option to <command>mysqld</command>.
         </para>
       </listitem>
 


Modified: trunk/refman-4.1/news-4.0.xml
===================================================================
--- trunk/refman-4.1/news-4.0.xml	2009-02-15 04:17:57 UTC (rev 13767)
+++ trunk/refman-4.1/news-4.0.xml	2009-02-15 04:18:11 UTC (rev 13768)
Changed blocks: 2, Lines Added: 5, Lines Deleted: 3; 1076 bytes

@@ -4279,7 +4279,8 @@
 
       <listitem>
         <para>
-          Added option <option role="mysqld">--sql-mode=NO_DIR_IN_CREATE</option> to
+          Added option
+          <option role="mysqld">--sql-mode=NO_DIR_IN_CREATE</option> to
           make it possible for slaves to ignore <literal>INDEX
           DIRECTORY</literal> and <literal>DATA DIRECTORY</literal>
           options given to <literal role="stmt">CREATE TABLE</literal>.

@@ -7329,8 +7330,9 @@
 
       <listitem>
         <para>
-          Fixed bug that prevented <option role="mysqld">--chroot</option>
-          command-line option of <command>mysqld</command> from working.
+          Fixed bug that prevented
+          <option role="mysqld">--chroot</option> command-line option of
+          <command>mysqld</command> from working.
         </para>
       </listitem>
 


Modified: trunk/refman-4.1/optimization.xml
===================================================================
--- trunk/refman-4.1/optimization.xml	2009-02-15 04:17:57 UTC (rev 13767)
+++ trunk/refman-4.1/optimization.xml	2009-02-15 04:18:11 UTC (rev 13768)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 936 bytes

@@ -12796,9 +12796,9 @@
             For a version of <command>mysqld</command> that has been
             compiled with <option>--with-debug=full</option>, you can
             disable memory checking at runtime by starting it with the
-            <option role="mysqld">--skip-safemalloc</option> option. The execution
-            speed should then be close to that obtained when configuring
-            with <option>--with-debug</option>.
+            <option role="mysqld">--skip-safemalloc</option> option. The
+            execution speed should then be close to that obtained when
+            configuring with <option>--with-debug</option>.
           </para>
         </listitem>
 


Modified: trunk/refman-4.1/programs-client.xml
===================================================================


Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 113 bytes


Thread
svn commit - mysqldoc@docsrva: r13768 - in trunk: . dynamic-docs/changelog refman-4.1 refman-5.0 refman-5.1 refman-5.1-maria refman-6.0paul.dubois15 Feb