bk commit - mysqldoc@docsrva tree (jon:1.2885)

[jon]

Below is the list of changes that have just been committed into a local
mysqldoc repository of jon. When jon 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.2885 05/06/26 11:27:19 jon@stripped +3 -0
  column-types.xml: storage-requirements: Fixed typo.
  Sync refman-4.1 & refman-5.0 to refman.

  refman/column-types.xml
    1.6 05/06/26 11:27:18 jon@stripped +1 -1
    storage-requirements: Fixed typo.

  refman-5.0/column-types.xml
    1.6 05/06/26 11:27:18 jon@stripped +1 -1
    storage-requirements: Fixed typo.
    Sync to refman.

  refman-4.1/column-types.xml
    1.6 05/06/26 11:27:17 jon@stripped +1 -1
    storage-requirements: Fixed typo.
    Sync to refman.

# 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:	jon
# Host:	gigan.site
# Root:	/home/jon/bk/mysqldoc

--- 1.5/refman-4.1/column-types.xml	2005-06-23 17:10:49 +10:00
+++ 1.6/refman-4.1/column-types.xml	2005-06-26 11:27:17 +10:00
@@ -5163,7 +5163,7 @@
   <para>
    As of MySQL 5.0.3, the <literal>NDBCLUSTER</literal> engine supports
    only fixed-width columns. This means that a
-   <literal>VARCHAR</literal> column from a table in a MySQL CLuster
+   <literal>VARCHAR</literal> column from a table in a MySQL Cluster
    will behave almost as if it were of type <literal>CHAR</literal>
    (except that each record still has one extra byte overhead). For
    example, in a Cluster table, <emphasis>each</emphasis> record in a

--- 1.5/refman-5.0/column-types.xml	2005-06-23 17:10:51 +10:00
+++ 1.6/refman-5.0/column-types.xml	2005-06-26 11:27:18 +10:00
@@ -5163,7 +5163,7 @@
   <para>
    As of MySQL 5.0.3, the <literal>NDBCLUSTER</literal> engine supports
    only fixed-width columns. This means that a
-   <literal>VARCHAR</literal> column from a table in a MySQL CLuster
+   <literal>VARCHAR</literal> column from a table in a MySQL Cluster
    will behave almost as if it were of type <literal>CHAR</literal>
    (except that each record still has one extra byte overhead). For
    example, in a Cluster table, <emphasis>each</emphasis> record in a

--- 1.5/refman/column-types.xml	2005-06-23 17:09:52 +10:00
+++ 1.6/refman/column-types.xml	2005-06-26 11:27:18 +10:00
@@ -5163,7 +5163,7 @@
   <para>
    As of MySQL 5.0.3, the <literal>NDBCLUSTER</literal> engine supports
    only fixed-width columns. This means that a
-   <literal>VARCHAR</literal> column from a table in a MySQL CLuster
+   <literal>VARCHAR</literal> column from a table in a MySQL Cluster
    will behave almost as if it were of type <literal>CHAR</literal>
    (except that each record still has one extra byte overhead). For
    example, in a Cluster table, <emphasis>each</emphasis> record in a