From: jon Date: May 18 2007 4:01pm Subject: svn commit - mysqldoc@docsrva: r6533 - trunk/refman-5.0 List-Archive: http://lists.mysql.com/commits/27003 Message-Id: <200705181601.l4IG1IVM009205@docsrva.mysql.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Author: jstephens Date: 2007-05-18 18:01:17 +0200 (Fri, 18 May 2007) New Revision: 6533 Log: Some minor fixups - 5.0 version. Modified: trunk/refman-5.0/mysql-cluster-limitations-working.xml Modified: trunk/refman-5.0/mysql-cluster-limitations-working.xml =================================================================== --- trunk/refman-5.0/mysql-cluster-limitations-working.xml 2007-05-18 15:36:42 UTC (rev 6532) +++ trunk/refman-5.0/mysql-cluster-limitations-working.xml 2007-05-18 16:01:17 UTC (rev 6533) Changed blocks: 1, Lines Added: 10, Lines Deleted: 12; 1892 bytes @@ -19,18 +19,16 @@ In the sections that follow, we discuss known limitations in MySQL - ¤t-series; Cluster and &mccge-series; releases as compared - with the features available when using the MyISAM - and InnoDB storage engines. Currently, there are - no plans to address these in coming releases of MySQL - ¤t-series; or &mccge-series;; however, we will attempt to - supply fixes for these issues in subsequent release series. If you - check the Cluster category in the MySQL bugs database - at , you can find known bugs - which (if marked ¤t-series;) we intend to - correct in upcoming releases of MySQL ¤t-series;. Some of - these issues may be addressed in &mccge-series; and the fixes - included in a future mainline MySQL Cluster version. + ¤t-series; Cluster releases as compared with the features + available when using the MyISAM and + InnoDB storage engines. Currently, there are no + plans to address these in coming releases of MySQL ¤t-series;; + however, we will attempt to supply fixes for these issues in + subsequent release series. If you check the Cluster + category in the MySQL bugs database at + , you can find known bugs which + (if marked ¤t-series;) we intend to correct in + upcoming releases of MySQL ¤t-series;.