bk commit - mysqldoc tree (mats:1.2378)

[Mats Kindahl]

Below is the list of changes that have just been committed into a local
mysqldoc repository of mats. When mats 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.2378 04/12/03 13:14:41 mats@stripped +1 -0
  Bug#6391 (binlog-do-db rules ignored)
    Documented change in semantics for CREATE/ALTER/DROP DATABASE
    statements. These statements are now written to binlog based on the
    database created/altered/dropped rather than on the current database.

  Docs/manual.texi
    1.2241 04/12/03 13:11:08 mats@stripped +18 -2
    Documented change in semantics for CREATE/ALTER/DROP DATABASE
    statements.

# 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:	mats
# Host:	tuna.ndb.mysql.com
# Root:	/orca/space/bk/b6391-mysqldoc

--- 1.2240/Docs/manual.texi	2004-11-25 14:57:31 +01:00
+++ 1.2241/Docs/manual.texi	2004-12-03 13:11:08 +01:00
@@ -28571,6 +28571,10 @@
 other databases that are not explicitly mentioned are ignored.  If you use
 this, you should ensure that you only do updates in the current database.
 
+Observe that there is an exception to the @code{CREATE/ALTER/DROP
+DATABASE} statements, which use the database manipulated to decide if
+it should log the statement rather than the current database.
+
 An example of what does not work as you might expect: If the server is
 started with @code{binlog-do-db=sales}, and you do
 @code{USE prices; UPDATE sales.january SET amount=amount+1000;},
@@ -28588,13 +28592,21 @@
 @code{USE prices; UPDATE sales.january SET amount=amount+1000;},
 this statement will be written into the binary log.
 
+Similar to the case for @code{--binlog-do-db}, there is an exception
+to the @code{CREATE/ALTER/DROP DATABASE} statements, which use the
+database manipulated to decide if it should log the statement rather
+than the current database.
+
 @end table
 
 To log or ignore multiple databases, specify the appropriate option multiple
 times, once for each database.
 
-The rules for logging or ignoring updates to the binary log are evaluated in
-the following order:
+The rules for logging or ignoring updates to the binary log are
+evaluated according to the following rules. Observe that for
+@code{CREATE/ALTER/DROP DATABASE} statements, the database being
+@emph{manipulated}, rather than the @emph{current database}, is used
+instead of the current database in the rules below.
 
 @enumerate
 @item
@@ -93561,6 +93573,10 @@
 @item
 Fixed a bug which caused a crash when only the slave I/O thread was
 stopped and started. (Bug #6148)
+@item
+Changed semantics of @code{CREATE/ALTER/DROP DATABASE} statements so
+that replication of @code{CREATE DATABASE} is possible when using
+@code{--binlog-do-db} and @code{--binlog-ignore-db}. (Bug #6391)
 @end itemize
 
 @node News-4.1.7, News-4.1.6, News-4.1.8, News-4.1.x