svn commit - mysqldoc@docsrva: r1029 - in trunk: . refman-5.1

[paul]

Author: paul
Date: 2006-01-25 05:15:04 +0100 (Wed, 25 Jan 2006)
New Revision: 1029

Log:
 r6662@frost:  paul | 2006-01-24 21:27:05 -0600
 5.1: silent column changes no longer happen. This section
 isn't needed any more.


Modified:
   trunk/
   trunk/refman-5.1/introduction.xml
   trunk/refman-5.1/sql-syntax.xml


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6660
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2497
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6662
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2497

Modified: trunk/refman-5.1/introduction.xml
===================================================================
--- trunk/refman-5.1/introduction.xml	2006-01-25 03:22:41 UTC (rev 1028)
+++ trunk/refman-5.1/introduction.xml	2006-01-25 04:15:04 UTC (rev 1029)
@@ -1302,7 +1302,7 @@
             In some cases, <literal>CHAR</literal> columns are silently
             converted to <literal>VARCHAR</literal> columns when you
             define a table or alter its structure. (This is fixed in
-            MySQL 5.0.3). See <xref linkend="silent-column-changes"/>.
+            MySQL 5.0.3).
           </para>
         </listitem>
 

Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml	2006-01-25 03:22:41 UTC (rev 1028)
+++ trunk/refman-5.1/sql-syntax.xml	2006-01-25 04:15:04 UTC (rev 1029)
@@ -3402,25 +3402,6 @@
         inserts during <literal>CREATE TABLE ... SELECT</literal>.
       </para>
 
-      <section id="silent-column-changes">
-
-        <title>&title-silent-column-changes;</title>
-
-        <indexterm>
-          <primary>silent column changes</primary>
-        </indexterm>
-
-        <para>
-          In some cases, older versions of MySQL silently changed column
-          specifications from those given in a <literal>CREATE
-          TABLE</literal> or <literal>ALTER TABLE</literal> statement.
-          No such changes are made by MySQL &current-series;, and an
-          error occurs if a column cannot be created using the specified
-          data type.
-        </para>
-
-      </section>
-
     </section>
 
     <section id="drop-database">
@@ -10135,13 +10116,6 @@
         <literal>AUTO_INCREMENT</literal> keyword.
       </para>
 
-      <para>
-        If the data types are different from what you expect them to be
-        based on a <literal>CREATE TABLE</literal> statement, note that
-        MySQL sometimes changes data types. See
-        <xref linkend="silent-column-changes"/>.
-      </para>
-
       <indexterm>
         <primary>Oracle compatibility</primary>
       </indexterm>
@@ -15138,14 +15112,6 @@
         </para>
 
         <para>
-          If the data types differ from what you expect them to be based
-          on your <literal>CREATE TABLE</literal> statement, note that
-          MySQL sometimes changes data types when you create or alter a
-          table. The conditions for which this occurs are described in
-          <xref linkend="silent-column-changes"/>.
-        </para>
-
-        <para>
           The <literal>FULL</literal> keyword causes the output to
           include the privileges you have as well as any per-column
           comments for each column.