svn commit - mysqldoc@docsrva: r10717 - in trunk: . it/refman-5.1 pt/refman-5.1 refman-4.1 refman-5.0 refman-5.1 refman-6.0

[paul]

Author: paul
Date: 2008-05-12 18:45:29 +0200 (Mon, 12 May 2008)
New Revision: 10717

Log:
 r31213@arctic:  paul | 2008-05-12 11:36:48 -0500
 Compressed string storage: Use a binary string data type, not only because
 of trailing space issues for non-binary string types (as we already stated)
 but because character set conversion may occur. (MLord)


Modified:
   trunk/it/refman-5.1/functions-core.xml
   trunk/pt/refman-5.1/functions-core.xml
   trunk/refman-4.1/functions-core.xml
   trunk/refman-5.0/functions-core.xml
   trunk/refman-5.1/functions-core.xml
   trunk/refman-6.0/functions-core.xml

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


Modified: trunk/it/refman-5.1/functions-core.xml
===================================================================
--- trunk/it/refman-5.1/functions-core.xml	2008-05-12 16:45:12 UTC (rev 10716)
+++ trunk/it/refman-5.1/functions-core.xml	2008-05-12 16:45:29 UTC (rev 10717)
Changed blocks: 2, Lines Added: 13, Lines Deleted: 7; 2128 bytes

@@ -14884,10 +14884,13 @@
           The encryption and compression functions return binary
           strings. For many of these functions, the result might contain
           arbitrary byte values. If you want to store these results, use
-          a <literal>BLOB</literal> column rather than a
-          <literal>CHAR</literal> or <literal>VARCHAR</literal>
column
-          to avoid potential problems with trailing space removal that
-          would change data values.
+          a column with a <literal>VARBINARY</literal> or
+          <literal>BLOB</literal> binary string data type. This will
+          avoid potential problems with trailing space removal or
+          character set conversion that would change data values, such
+          as may occur if you use a non-binary string data type
+          (<literal>CHAR</literal>, <literal>VARCHAR</literal>,
+          <literal>TEXT</literal>).
         </para>
       </note>
 

@@ -15076,10 +15079,13 @@
                 extra <quote><literal>.</literal></quote>
character is
                 added to avoid problems with endspace trimming should
                 the result be stored in a <literal>CHAR</literal> or
-                <literal>VARCHAR</literal> column. (Use of
+                <literal>VARCHAR</literal> column. (However, use of
+                non-binary string data types such as
                 <literal>CHAR</literal> or
<literal>VARCHAR</literal> to
-                store compressed strings is not recommended. It is
-                better to use a <literal>BLOB</literal> column instead.)
+                store compressed strings is not recommended anyway
+                because character set conversion may occur. Use a
+                <literal>VARBINARY</literal> or
<literal>BLOB</literal>
+                binary string column instead.)
               </para>
             </listitem>
 


Modified: trunk/pt/refman-5.1/functions-core.xml
===================================================================
--- trunk/pt/refman-5.1/functions-core.xml	2008-05-12 16:45:12 UTC (rev 10716)
+++ trunk/pt/refman-5.1/functions-core.xml	2008-05-12 16:45:29 UTC (rev 10717)
Changed blocks: 2, Lines Added: 13, Lines Deleted: 7; 2128 bytes

@@ -14884,10 +14884,13 @@
           The encryption and compression functions return binary
           strings. For many of these functions, the result might contain
           arbitrary byte values. If you want to store these results, use
-          a <literal>BLOB</literal> column rather than a
-          <literal>CHAR</literal> or <literal>VARCHAR</literal>
column
-          to avoid potential problems with trailing space removal that
-          would change data values.
+          a column with a <literal>VARBINARY</literal> or
+          <literal>BLOB</literal> binary string data type. This will
+          avoid potential problems with trailing space removal or
+          character set conversion that would change data values, such
+          as may occur if you use a non-binary string data type
+          (<literal>CHAR</literal>, <literal>VARCHAR</literal>,
+          <literal>TEXT</literal>).
         </para>
       </note>
 

@@ -15076,10 +15079,13 @@
                 extra <quote><literal>.</literal></quote>
character is
                 added to avoid problems with endspace trimming should
                 the result be stored in a <literal>CHAR</literal> or
-                <literal>VARCHAR</literal> column. (Use of
+                <literal>VARCHAR</literal> column. (However, use of
+                non-binary string data types such as
                 <literal>CHAR</literal> or
<literal>VARCHAR</literal> to
-                store compressed strings is not recommended. It is
-                better to use a <literal>BLOB</literal> column instead.)
+                store compressed strings is not recommended anyway
+                because character set conversion may occur. Use a
+                <literal>VARBINARY</literal> or
<literal>BLOB</literal>
+                binary string column instead.)
               </para>
             </listitem>
 


Modified: trunk/refman-4.1/functions-core.xml
===================================================================
--- trunk/refman-4.1/functions-core.xml	2008-05-12 16:45:12 UTC (rev 10716)
+++ trunk/refman-4.1/functions-core.xml	2008-05-12 16:45:29 UTC (rev 10717)
Changed blocks: 2, Lines Added: 13, Lines Deleted: 7; 2119 bytes

@@ -13413,10 +13413,13 @@
           The encryption and compression functions return binary
           strings. For many of these functions, the result might contain
           arbitrary byte values. If you want to store these results, use
-          a <literal>BLOB</literal> column rather than a
-          <literal>CHAR</literal> or <literal>VARCHAR</literal>
column
-          to avoid potential problems with trailing space removal that
-          would change data values.
+          a column with a <literal>VARBINARY</literal> or
+          <literal>BLOB</literal> binary string data type. This will
+          avoid potential problems with trailing space removal or
+          character set conversion that would change data values, such
+          as may occur if you use a non-binary string data type
+          (<literal>CHAR</literal>, <literal>VARCHAR</literal>,
+          <literal>TEXT</literal>).
         </para>
       </note>
 

@@ -13606,10 +13609,13 @@
                 extra <quote><literal>.</literal></quote>
character is
                 added to avoid problems with endspace trimming should
                 the result be stored in a <literal>CHAR</literal> or
-                <literal>VARCHAR</literal> column. (Use of
+                <literal>VARCHAR</literal> column. (However, use of
+                non-binary string data types such as
                 <literal>CHAR</literal> or
<literal>VARCHAR</literal> to
-                store compressed strings is not recommended. It is
-                better to use a <literal>BLOB</literal> column instead.)
+                store compressed strings is not recommended anyway
+                because character set conversion may occur. Use a
+                <literal>VARBINARY</literal> or
<literal>BLOB</literal>
+                binary string column instead.)
               </para>
             </listitem>
 


Modified: trunk/refman-5.0/functions-core.xml
===================================================================
--- trunk/refman-5.0/functions-core.xml	2008-05-12 16:45:12 UTC (rev 10716)
+++ trunk/refman-5.0/functions-core.xml	2008-05-12 16:45:29 UTC (rev 10717)
Changed blocks: 2, Lines Added: 16, Lines Deleted: 10; 2393 bytes

@@ -13610,13 +13610,16 @@
 
       <note>
         <para>
-          The encryption and compression functions return binary
-          strings. For many of these functions, the result might contain
-          arbitrary byte values. If you want to store these results, use
-          a <literal>BLOB</literal> column rather than a
-          <literal>CHAR</literal> or (before MySQL 5.0.3)
-          <literal>VARCHAR</literal> column to avoid potential problems
-          with trailing space removal that would change data values.
+            The encryption and compression functions return binary
+            strings. For many of these functions, the result might contain
+            arbitrary byte values. If you want to store these results, use
+           a column with a <literal>VARBINARY</literal> or
+           <literal>BLOB</literal> binary string data type. This will
+           avoid potential problems with trailing space removal or
+           character set conversion that would change data values, such
+           as may occur if you use a non-binary string data type
+           (<literal>CHAR</literal>, <literal>VARCHAR</literal>,
+           <literal>TEXT</literal>).
         </para>
       </note>
 

@@ -13805,10 +13808,13 @@
                 extra <quote><literal>.</literal></quote>
character is
                 added to avoid problems with endspace trimming should
                 the result be stored in a <literal>CHAR</literal> or
-                <literal>VARCHAR</literal> column. (Use of
+                <literal>VARCHAR</literal> column. (However, use of
+                non-binary string data types such as
                 <literal>CHAR</literal> or
<literal>VARCHAR</literal> to
-                store compressed strings is not recommended. It is
-                better to use a <literal>BLOB</literal> column instead.)
+                store compressed strings is not recommended anyway
+                because character set conversion may occur. Use a
+                <literal>VARBINARY</literal> or
<literal>BLOB</literal>
+                binary string column instead.)
               </para>
             </listitem>
 


Modified: trunk/refman-5.1/functions-core.xml
===================================================================
--- trunk/refman-5.1/functions-core.xml	2008-05-12 16:45:12 UTC (rev 10716)
+++ trunk/refman-5.1/functions-core.xml	2008-05-12 16:45:29 UTC (rev 10717)
Changed blocks: 2, Lines Added: 13, Lines Deleted: 7; 2119 bytes

@@ -14884,10 +14884,13 @@
           The encryption and compression functions return binary
           strings. For many of these functions, the result might contain
           arbitrary byte values. If you want to store these results, use
-          a <literal>BLOB</literal> column rather than a
-          <literal>CHAR</literal> or <literal>VARCHAR</literal>
column
-          to avoid potential problems with trailing space removal that
-          would change data values.
+          a column with a <literal>VARBINARY</literal> or
+          <literal>BLOB</literal> binary string data type. This will
+          avoid potential problems with trailing space removal or
+          character set conversion that would change data values, such
+          as may occur if you use a non-binary string data type
+          (<literal>CHAR</literal>, <literal>VARCHAR</literal>,
+          <literal>TEXT</literal>).
         </para>
       </note>
 

@@ -15076,10 +15079,13 @@
                 extra <quote><literal>.</literal></quote>
character is
                 added to avoid problems with endspace trimming should
                 the result be stored in a <literal>CHAR</literal> or
-                <literal>VARCHAR</literal> column. (Use of
+                <literal>VARCHAR</literal> column. (However, use of
+                non-binary string data types such as
                 <literal>CHAR</literal> or
<literal>VARCHAR</literal> to
-                store compressed strings is not recommended. It is
-                better to use a <literal>BLOB</literal> column instead.)
+                store compressed strings is not recommended anyway
+                because character set conversion may occur. Use a
+                <literal>VARBINARY</literal> or
<literal>BLOB</literal>
+                binary string column instead.)
               </para>
             </listitem>
 


Modified: trunk/refman-6.0/functions-core.xml
===================================================================
--- trunk/refman-6.0/functions-core.xml	2008-05-12 16:45:12 UTC (rev 10716)
+++ trunk/refman-6.0/functions-core.xml	2008-05-12 16:45:29 UTC (rev 10717)
Changed blocks: 2, Lines Added: 13, Lines Deleted: 7; 2119 bytes

@@ -15284,10 +15284,13 @@
           The encryption and compression functions return binary
           strings. For many of these functions, the result might contain
           arbitrary byte values. If you want to store these results, use
-          a <literal>BLOB</literal> column rather than a
-          <literal>CHAR</literal> or <literal>VARCHAR</literal>
column
-          to avoid potential problems with trailing space removal that
-          would change data values.
+          a column with a <literal>VARBINARY</literal> or
+          <literal>BLOB</literal> binary string data type. This will
+          avoid potential problems with trailing space removal or
+          character set conversion that would change data values, such
+          as may occur if you use a non-binary string data type
+          (<literal>CHAR</literal>, <literal>VARCHAR</literal>,
+          <literal>TEXT</literal>).
         </para>
       </note>
 

@@ -15477,10 +15480,13 @@
                 extra <quote><literal>.</literal></quote>
character is
                 added to avoid problems with endspace trimming should
                 the result be stored in a <literal>CHAR</literal> or
-                <literal>VARCHAR</literal> column. (Use of
+                <literal>VARCHAR</literal> column. (However, use of
+                non-binary string data types such as
                 <literal>CHAR</literal> or
<literal>VARCHAR</literal> to
-                store compressed strings is not recommended. It is
-                better to use a <literal>BLOB</literal> column instead.)
+                store compressed strings is not recommended anyway
+                because character set conversion may occur. Use a
+                <literal>VARBINARY</literal> or
<literal>BLOB</literal>
+                binary string column instead.)
               </para>
             </listitem>