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

[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.2671 05/05/17 13:19:53 jon@stripped +1 -0
  Merge bk://mysqldoc@stripped
  into gigan.homedns.org:/home/jon/bk/mysqldoc

  Docs/manual.texi
    1.2860 05/05/17 13:19:51 jon@stripped +0 -0
    Auto merged

# 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/RESYNC

--- 1.2859/Docs/manual.texi	2005-05-17 13:00:32 +10:00
+++ 1.2860/Docs/manual.texi	2005-05-17 13:19:51 +10:00
@@ -76082,7 +76082,8 @@
   database tables, system tables, indexes and BLOBs.
   @item The maximum number of attributes per table is limited to 128.
   @item The maximum permitted size of any one row is 8k, not including data
-  stored in BLOB columns.
+  stored in BLOB columns. We expect to increase this to approximately 32k in
+  MySQL 5.1.
   @item The maximum number of attributes per key is 32.
   @end itemize
 
@@ -76095,8 +76096,8 @@
 
 @item @strong{Performance and limitation-related issues}:
   @itemize @asis
-  @item The query cache is disabled, since it is not invalidated if an update occurs
-  on a different MySQL server.
+  @item The query cache is disabled, since it is not invalidated if an update
+  occurs on a different MySQL server.
   @item There are query performance issues due to sequential access to the NDB
   storage engine; it is also relatively more expensive to do many range scans
   than it is with either MyISAM or InnoDB.
@@ -76305,6 +76306,15 @@
 
 @end itemize
 
+In addition, we are working to increase the 8k size limit for rows containing
+columns of types other than BLOB or TEXT in Cluster tables. This is due to the
+fact that rows are currently fixed in size and the page size is 32,768 bytes
+(minus 128 bytes for the row header). Currently this means that if we allowed
+more than 8k per record, any remaining space (up to approximately 14,000 bytes)
+would be left empty. In MySQL 5.1, we plan to fix this limitation so that using
+more than 8k in a given row does not result in the remainder of the page being
+wasted.
+
 @c  *** END CLUSTER IN 5.0/5.1  ***
 
 
@@ -101935,10 +101945,10 @@
 @item
 @code{CAST(string_argument AS UNSIGNED)} didn't work for big integers above the
 signed range.  Now this function and @code{CAST(string_argument AS SIGNED)}
-also produces warnings for wrong string arguments. (Bug #7036) 
+also produces warnings for wrong string arguments. (Bug #7036)
 @item
 Fixed compile problem with MinGW. Thanks to Nils Durner for patch!
-(Bug #8872) 
+(Bug #8872)
 @item
 MySQL doesn't anymore automaticly block IP's for which
 @code{gethostbyname_r()} fails when the reason is that the DNS server is down.