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.1816 04/07/08 22:36:38 guilhem@stripped +1 -0
someone had forgotten to specify that --log-warnings is enabled by default as of 4.0.19, not only as of 4.1.2
Docs/manual.texi
1.1810 04/07/08 22:36:36 guilhem@stripped +9 -5
someone had forgotten to specify that --log-warnings is enabled by default as of 4.0.19, not only as of 4.1.2
# 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.1809/Docs/manual.texi 2004-07-08 20:05:48 +02:00
+++ 1.1810/Docs/manual.texi 2004-07-08 22:36:36 +02:00
@@ -18818,8 +18818,8 @@
Enabling this option is recommended, for example, if you
use replication (you will get more information about what is happening,
such as messages about network failures and reconnections).
-This option is enabled by default as of MySQL 4.1.2; to disable it, use
-@code{--skip-log-warnings}.
+This option is enabled by default as of MySQL 4.0.19 and 4.1.2; to disable it,
+use @code{--skip-log-warnings}.
@xref{Communication errors}.
This option was named @code{--warnings} before MySQL 4.0.
@@ -29139,7 +29139,8 @@
start the slave server with the @code{--skip-slave-start} option so that it
doesn't immediately try to connect to its master.
You also may want to start the slave server with the
-@code{--log-warnings} option, to get more messages about
+@code{--log-warnings} option (enabled by default as of MySQL 4.0.19 and 4.1.2),
+to get more messages about
problems (for example, network or connection problems).
@item
@@ -29778,8 +29779,8 @@
Makes the slave print more messages about what it is doing. For
example, it will warn you that it succeeded in reconnecting after a
network/connection failure, and warn you about how each slave thread started.
-This option is enabled by default as of MySQL 4.1.2; to disable it, use
-@code{--skip-log-warnings}.
+This option is enabled by default as of MySQL 4.0.19 and 4.1.2; to disable it,
+use @code{--skip-log-warnings}.
This option is not limited to replication use only. It produces warnings
across a spectrum of server activities.
@@ -85692,6 +85693,9 @@
EXISTS} instead of @code{DROP TEMPORARY TABLE}, for more robustness.
@item
Added option @code{--replicate-same-server-id}.
+@item
+The @code{--log-warnings} server option now is enabled by default.
+Disable with @code{--skip-log-warnings}.
@end itemize
Bugs fixed:
| Thread |
|---|
| • bk commit - mysqldoc tree (guilhem:1.1816) | guilhem | 8 Jul |
