bk commit - mysqldoc tree (guilhem:1.1224)

[guilhem]

Below is the list of changes that have just been committed into a local
mysqldoc repository of guilhem. When guilhem 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.1224 04/02/05 13:38:52 guilhem@stripped +1 -0
  Info about NO_DIR_IN_CREATE in "Replication features and Known problems"
  (this SQL mode is already documented in the SQL_MODE section).

  Docs/manual.texi
    1.1130 04/02/05 13:38:50 guilhem@stripped +8 -0
    Info about NO_DIR_IN_CREATE in "Replication features and Known problems"
    (this SQL mode is already documented in the SQL_MODE section).

# 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:	guilhem
# Host:	gbichot2.local
# Root:	/home/mysql_src/mysqldoc

--- 1.1129/Docs/manual.texi	Thu Feb  5 15:31:11 2004
+++ 1.1130/Docs/manual.texi	Thu Feb  5 13:38:50 2004
@@ -24746,6 +24746,14 @@
 The slave can connect to the master using SSL, if the master and slave
 are both 4.1.1 or newer.
 @item
+If a @code{DATA DIRECTORY} or @code{INDEX DIRECTORY} clause was used in a
+@code{CREATE TABLE} on master, then these clauses will be used too on
+slave. Starting from MySQL 4.0.15 there is a @code{SQL_MODE} mode called
+@code{NO_DIR_IN_CREATE}; if the slave server is run in this mode, it will
+simply cut off the clauses before replicating the @code{CREATE TABLE} (so the
+MyISAM data and index files will be created in the slave's @code{datadir}
+directory).
+@item
 Though we have never heard of it actually occurring, it is theoretically
 possible for the data on the master and slave to become different if a
 query is designed in such a way that the data modification is