bk commit - mysqldoc tree (1.328)

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.328 03/04/29 17:02:41 guilhem@xxxxxxxxx +1 -0
  Note about "PASSWORD() not well replicated since 4.1".

  Docs/manual.texi
    1.305 03/04/29 17:02:40 guilhem@xxxxxxxxx +9 -4
    Note about "PASSWORD() not well replicated since 4.1".

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

--- 1.304/Docs/manual.texi      Tue Apr 29 00:29:16 2003
+++ 1.305/Docs/manual.texi      Tue Apr 29 17:02:40 2003
@@ -25873,7 +25873,12 @@
 @code{LAST_INSERT_ID()}, and @code{TIMESTAMP} values.
 @item
 @code{USER()} and @code{CONNECTION_ID()} and @code{LOAD_FILE()} functions
-are replicated without changes and will thus not work reliable on the slave.
+are replicated without changes and will thus not work reliably on the
+slave. The new @code{PASSWORD()} function in MySQL 4.1, because it has some
+randomness in it, has the same problem; if you really want to use the
+MySQL @code{PASSWORD()} functions (you may prefer using @code{MD5} or
+@code{SHA1}, @pxref{Miscellaneous functions}), start you master and
+slave with option @code{--old-password} or use @code{OLD_PASSWORD()}.
 @item
 @code{SQL_MODE}, @code{FOREIGN_KEY_CHECKS} and @code{TABLE_TYPE}
 variables are not replicated.
@@ -26434,8 +26439,8 @@
 @node RESET SLAVE
 @subsubsection @code{RESET SLAVE} (slave)
 Makes the slave forget its replication position in the master's binlogs,
-deletes the @code{master.info} and
-@code{relay-log.info} files, all relay logs, starts a new relay log.
+deletes the @file{master.info} and
+@file{relay-log.info} files, all relay logs, starts a new relay log.
 Connection information (@code{master-host} et al.) is not cleared in
 memory and
 will be reused if you @code{START SLAVE} later. But if you shutdown
@@ -26553,7 +26558,7 @@
 Then the server will read and execute its own binlogs, thus achieving
 crash recovery.
 Once the recovery is finished, run @code{STOP SLAVE}, shutdown the
-server, delete @code{master.info} and @code{relay-log.info},
+server, delete @file{master.info} and @file{relay-log.info},
 and restart the server with its original options.
 For the moment, specifying @code{MASTER_HOST} (even with a dummy value) is 
compulsory
 to make the server think he is a slave, and giving the server a new,

-- 
MySQL Internals Mailing List
For list archives: http://lists.mysql.com/internals
To unsubscribe:    
http://lists.mysql.com/internals?unsub=gcdmd-internals@xxxxxxxxxxx