svn commit - mysqldoc@docsrva: r308 - in trunk: refman-4.1 refman-5.0 refman-5.1

[jstephens]

Author: jstephens
Date: 2005-11-10 11:06:04 +0100 (Thu, 10 Nov 2005)
New Revision: 308

Log:

refman-4.1/column-types.xml,
refman-5.0/column-types.xml,
refman-5.1/column-types.xml
  - Added note about bytes used by string column values and characters sets and 
    link to charset-unicode.



Modified:
   trunk/refman-4.1/column-types.xml
   trunk/refman-5.0/column-types.xml
   trunk/refman-5.1/column-types.xml

Modified: trunk/refman-4.1/column-types.xml
===================================================================
--- trunk/refman-4.1/column-types.xml	2005-11-10 05:44:08 UTC (rev 307)
+++ trunk/refman-4.1/column-types.xml	2005-11-10 10:06:04 UTC (rev 308)
@@ -5128,6 +5128,18 @@
     </para>
 
     <para>
+      To calculate the number of <emphasis>bytes</emphasis> used to
+      store a particular <literal>CHAR</literal>,
+      <literal>VARCHAR</literal>, or <literal>TEXT</literal>
column
+      value in MySQL 4.1 (and later), you will need to take into account 
+      the character set in use for that column. In particular, when using 
+      Unicode, you must keep in mind that not all Unicode characters use 
+      the same number of bytes. For a breakdown of the storage used for 
+      different categories of Unicode characters, see 
+      <xref linkend="charset-unicode"/>.
+    </para>
+
+    <para>
       <emphasis role="bold">Note</emphasis>: The <literal>NDB
       Cluster</literal> engine supports only fixed-width columns. This
       means that a <literal>VARCHAR</literal> column from a table in a

Modified: trunk/refman-5.0/column-types.xml
===================================================================
--- trunk/refman-5.0/column-types.xml	2005-11-10 05:44:08 UTC (rev 307)
+++ trunk/refman-5.0/column-types.xml	2005-11-10 10:06:04 UTC (rev 308)
@@ -4991,6 +4991,18 @@
       store a <literal>TINYTEXT</literal> value requires
       <replaceable>L</replaceable> characters + 1 byte.
     </para>
+    
+    <para>
+      To calculate the number of <emphasis>bytes</emphasis> used to
+      store a particular <literal>CHAR</literal>,
+      <literal>VARCHAR</literal>, or <literal>TEXT</literal>
column
+      value, you will need to take into account the character set in use
+      for that column. In particular, when using Unicode, you must keep
+      in mind that not all Unicode characters use the same number of
+      bytes. For a breakdown of the storage used for different
+      categories of Unicode characters, see 
+      <xref linkend="charset-unicode"/>.
+    </para>
 
     <para>
       <emphasis role="bold">Note</emphasis>: In MySQL 5.0.3 and later,

Modified: trunk/refman-5.1/column-types.xml
===================================================================
--- trunk/refman-5.1/column-types.xml	2005-11-10 05:44:08 UTC (rev 307)
+++ trunk/refman-5.1/column-types.xml	2005-11-10 10:06:04 UTC (rev 308)
@@ -4833,6 +4833,18 @@
     </para>
 
     <para>
+      To calculate the number of <emphasis>bytes</emphasis> used to
+      store a particular <literal>CHAR</literal>,
+      <literal>VARCHAR</literal>, or <literal>TEXT</literal>
column
+      value, you will need to take into account the character set in use
+      for that column. In particular, when using Unicode, you must keep
+      in mind that not all Unicode characters use the same number of
+      bytes. For a breakdown of the storage used for different
+      categories of Unicode characters, see 
+      <xref linkend="charset-unicode"/>.
+    </para>
+
+    <para>
       <emphasis role="bold">Note</emphasis>: The
       <emphasis>effective</emphasis> maximum length for a
       <literal>VARCHAR</literal> column is 65,532 characters.