bk commit - mysqldoc tree (paul:1.2741)

[paul]

Below is the list of changes that have just been committed into a local
mysqldoc repository of paul. When paul 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.2741 05/03/18 11:33:37 paul@stripped +1 -0
  manual.texi:
    Note that ISAM has been dropped from 5.0.
    Additional information about removal of RAID in 5.0.

  Docs/manual.texi
    1.2576 05/03/18 11:32:47 paul@stripped +49 -5
    Note that ISAM has been dropped from 5.0.
    Additional information about removal of RAID in 5.0.

# 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:	paul
# Host:	frost.snake.net
# Root:	/Volumes/frost2/MySQL/bk/mysqldoc

--- 1.2575/Docs/manual.texi	2005-03-18 10:44:41 -06:00
+++ 1.2576/Docs/manual.texi	2005-03-18 11:32:47 -06:00
@@ -10512,7 +10512,8 @@
 Check the items in the change list found later in this section to see
 whether any of them might affect your applications.  Note particularly any
 that are marked @strong{Incompatible change}; these result in
-incompatibilities with earlier versions of MySQL.
+incompatibilities with earlier versions of MySQL, and may require your
+attention @emph{before you upgrade}.
 
 @item
 Read the 5.0 news items to see what significant new features you can use in
@@ -10569,9 +10570,38 @@
 
 @item
 @strong{Incompatible change:}
+Support for the @code{ISAM} storage engine has been removed.  If you have
+@code{ISAM} tables, you should convert them before upgrading.  For example,
+to convert an @code{ISAM} table to use the @code{MyISAM} storage engine,
+use this statement:
+
+@example
+ALTER TABLE @var{tbl_name} ENGINE = MyISAM;
+@end example
+
+Use a similar statement for each @code{ISAM} statement.
+
+@item
+@strong{Incompatible change:}
 Support for @code{RAID} options in @code{MyISAM} tables has been removed.
-If you have tables that use these options, you should dump them with
-@command{mysqldump} and reload them without the options.
+If you have tables that use these options, you should convert them before
+upgrading.  One way to do this is to dump them with @command{mysqldump},
+edit the dump file to remove the @code{RAID} options in the @code{CREATE
+TABLE} statements, and reload the dump file.  Another way to convert a table
+is to use @code{ALTER TABLE} to convert it to use a different storage
+engine.  The use @code{ALTER TABLE} to convert it back if you want to
+continue to use the table as a @code{MyISAM} table. This approach requires
+some care, however. It cannot be used if the table contains
+@code{MyISAM}-only features such as @code{FULLTEXT} indexes or columns with
+spatial data types.
+
+The @file{.MYD} files for @code{RAID} tables in a given database are stored
+under the database directory in subdirectories that have names consisting of
+two hex digits in the range from @code{00} to @code{ff}.  After converting
+all tables that use @code{RAID} options, these @code{RAID}-related
+subdirectories still will exist but can be removed.  Verify that they are
+empty, and then remove them manually.  (If they are not empty, there is some
+@code{RAID} table that has not been converted.)
 
 @end itemize
 
@@ -97166,9 +97196,14 @@
 @code{SQL_LOG_BIN} instead (or do nothing if the server is explicitly
 started with @code{--log-bin}).
 @item
+Support for the @code{ISAM} storage engine has been removed.  If you have
+@code{ISAM} tables, you should convert them before upgrading.
+@xref{Upgrading-from-4.1}.
+@item
 Support for @code{RAID} options in @code{MyISAM} tables has been removed.
-If you have tables that use these options, you should dump them with
-@command{mysqldump} and reload them without the options.
+If you have tables that use these options, you should convert them before
+upgrading.
+@xref{Upgrading-from-4.1}.
 @item
 User variable names are now case insensitive: If you do @code{SET
 @@a=10;} then @code{SELECT @@A;} now returns @code{10}.
@@ -97255,6 +97290,15 @@
 See @ref{UDF calling}, @ref{UDF aggr. calling}, and @ref{UDF security}.
 (Thanks to Stefano Di Paola @email{stefano.dipaola@@wisec.it} for finding
 and informing us about this issue.)
+@item
+Support for the @code{ISAM} storage engine has been removed.  If you have
+@code{ISAM} tables, you should convert them before upgrading.
+@xref{Upgrading-from-4.1}.
+@item
+Support for @code{RAID} options in @code{MyISAM} tables has been removed.
+If you have tables that use these options, you should convert them before
+upgrading.
+@xref{Upgrading-from-4.1}.
 @item
 Added support for @code{AVG(DISTINCT)}.
 @item