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/Install...urce_tree.html

ChangeSet
1.2616 05/02/26 21:52:16 jon (AT) gigan (DOT) homedns.org +1 -0
Cluster FAQ and Limitations: Corrected notes about
fixed column size. (Thanks to Harrison and Mikael.)

Docs/manual.texi
1.2437 05/02/26 21:52:12 jon (AT) gigan (DOT) homedns.org +7 -5
Cluster FAQ and Limitations: Corrected notes about
fixed column size. (Thanks to Harrison and Mikael.)

# 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.2436/Docs/manual.texi 2005-02-26 14:31:57 +10:00
+++ 1.2437/Docs/manual.texi 2005-02-26 21:52:12 +10:00
@@ -74538,10 +74538,11 @@
maximum length for an NDB Cluster table name is 122 characters less the
number of characters in the name of the database of which that table is a
part.)
- @item In MySQL CLuster 4.1 and 5.0, all rows are of fixed length. This means
+ @item In MySQL Cluster 4.1 and 5.0, all rows are of fixed length. This means
(for example) that if a table has one or more VARCHAR fields containing only
- relatively small values, more memory and disk space will be required than
- would be for the same table and data using the MyISAM engine.
+ relatively small values, more memory and disk space will be required when
+ using the NDB storage engine than would be for the same table and data using
+ the MyISAM engine. We are working to rectify this issue in MySQL Cluster 5.1.
@item The maximum number of metadata objects is limited to 1600, including
database tables, system tables, indexes and BLOBs.
@item The maximum number of attributes per table is limited to 128.
@@ -74984,8 +74985,9 @@
extensions}. In addition, there are some differences with regard to indexes when
used with NDB tables. @strong{Note}: In MySQL Cluster 4.1.10 and MySQL Cluster
5.0.3, tables have only fixed-width rows. This means that (for example) each
-record containing a @code{TEXT} column will will require 65,535 bytes of storage
-for that column, regardless of the size of the data stored therein.
+record containing a @code{VARCHAR(255)} column will will require 256 bytes of
+storage for that column, regardless of the size of the data stored therein. This
+issue is expected to be fixed in MySQL 5.1.

See @ref{MySQL Cluster Limitations in 4.1} for more information about these
issues.

--
MySQL Internals Mailing List
For list archives: http://lists.mysql.com/internals
To unsubscribe: http://lists.mysql.com/internals?uns...ie.nctu.edu.tw