List:Internals« Previous MessageNext Message »
From:paul Date:September 9 2005 7:21pm
Subject:bk commit - mysqldoc@docsrva tree (paul:1.3523)
View as plain text  
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.3523 05/09/09 14:21:04 paul@stripped +4 -0
  Don't promise perfect compatibility.

  refman/client-side-scripts.xml
    1.36 05/09/09 14:21:03 paul@stripped +10 -1
    Don't promise perfect compatibility.

  refman-5.1/client-side-scripts.xml
    1.22 05/09/09 14:21:03 paul@stripped +10 -1
    Sync.

  refman-5.0/client-side-scripts.xml
    1.23 05/09/09 14:21:03 paul@stripped +10 -1
    Sync.

  refman-4.1/client-side-scripts.xml
    1.35 05/09/09 14:21:03 paul@stripped +10 -1
    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.21/refman-5.1/client-side-scripts.xml	2005-09-09 12:56:41 -05:00
+++ 1.22/refman-5.1/client-side-scripts.xml	2005-09-09 14:21:03 -05:00
@@ -5077,7 +5077,7 @@
             </para>
 
             <para>
-              Produce output that is compatible with other database
+              Produce output that is more compatible with other database
               systems or with older MySQL servers. The value of
               <literal>name</literal> can be <literal>ansi</literal>,
               <literal>mysql323</literal>, <literal>mysql40</literal>,
@@ -5090,6 +5090,15 @@
               values, separate them by commas. These values have the
               same meaning as the corresponding options for setting the
               server SQL mode. See <xref linkend="server-sql-mode"/>.
+            </para>
+
+            <para>
+              This option does not guarantee compatibility with other
+              servers. It only enables those SQL mode values that are
+              currently available for making dump output more
+              compatible. For example,
+              <option>--compatible=oracle</option> does not map data
+              types to Oracle types or use Oracle comment syntax.
             </para>
           </listitem>
 

--- 1.34/refman-4.1/client-side-scripts.xml	2005-09-09 12:56:41 -05:00
+++ 1.35/refman-4.1/client-side-scripts.xml	2005-09-09 14:21:03 -05:00
@@ -5160,7 +5160,7 @@
             </para>
 
             <para>
-              Produce output that is compatible with other database
+              Produce output that is more compatible with other database
               systems or with older MySQL servers. The value of
               <literal>name</literal> can be <literal>ansi</literal>,
               <literal>mysql323</literal>, <literal>mysql40</literal>,
@@ -5173,6 +5173,15 @@
               values, separate them by commas. These values have the
               same meaning as the corresponding options for setting the
               server SQL mode. See <xref linkend="server-sql-mode"/>.
+            </para>
+
+            <para>
+              This option does not guarantee compatibility with other
+              servers. It only enables those SQL mode values that are
+              currently available for making dump output more
+              compatible. For example,
+              <option>--compatible=oracle</option> does not map data
+              types to Oracle types or use Oracle comment syntax.
             </para>
 
             <para>

--- 1.35/refman/client-side-scripts.xml	2005-09-09 12:56:41 -05:00
+++ 1.36/refman/client-side-scripts.xml	2005-09-09 14:21:03 -05:00
@@ -5175,7 +5175,7 @@
             </para>
 
             <para>
-              Produce output that is compatible with other database
+              Produce output that is more compatible with other database
               systems or with older MySQL servers. The value of
               <literal>name</literal> can be <literal>ansi</literal>,
               <literal>mysql323</literal>, <literal>mysql40</literal>,
@@ -5188,6 +5188,15 @@
               values, separate them by commas. These values have the
               same meaning as the corresponding options for setting the
               server SQL mode. See <xref linkend="server-sql-mode"/>.
+            </para>
+
+            <para>
+              This option does not guarantee compatibility with other
+              servers. It only enables those SQL mode values that are
+              currently available for making dump output more
+              compatible. For example,
+              <option>--compatible=oracle</option> does not map data
+              types to Oracle types or use Oracle comment syntax.
             </para>
 
             <para>

--- 1.22/refman-5.0/client-side-scripts.xml	2005-09-09 12:56:41 -05:00
+++ 1.23/refman-5.0/client-side-scripts.xml	2005-09-09 14:21:03 -05:00
@@ -5077,7 +5077,7 @@
             </para>
 
             <para>
-              Produce output that is compatible with other database
+              Produce output that is more compatible with other database
               systems or with older MySQL servers. The value of
               <literal>name</literal> can be <literal>ansi</literal>,
               <literal>mysql323</literal>, <literal>mysql40</literal>,
@@ -5090,6 +5090,15 @@
               values, separate them by commas. These values have the
               same meaning as the corresponding options for setting the
               server SQL mode. See <xref linkend="server-sql-mode"/>.
+            </para>
+
+            <para>
+              This option does not guarantee compatibility with other
+              servers. It only enables those SQL mode values that are
+              currently available for making dump output more
+              compatible. For example,
+              <option>--compatible=oracle</option> does not map data
+              types to Oracle types or use Oracle comment syntax.
             </para>
           </listitem>
 
Thread
bk commit - mysqldoc@docsrva tree (paul:1.3523)paul9 Sep