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.2961 05/07/08 09:38:05 paul@stripped +4 -0
Format.
refman/triggers.xml
1.5 05/07/08 09:38:04 paul@stripped +6 -6
Format.
refman/replication.xml
1.4 05/07/08 09:38:03 paul@stripped +11 -11
Format.
refman-5.0/triggers.xml
1.5 05/07/08 09:38:03 paul@stripped +6 -6
Format.
refman-5.0/replication.xml
1.4 05/07/08 09:38:03 paul@stripped +11 -11
Format.
# 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.3/refman-5.0/replication.xml 2005-07-08 09:35:43 -05:00
+++ 1.4/refman-5.0/replication.xml 2005-07-08 09:38:03 -05:00
@@ -1760,9 +1760,9 @@
The following list provides details about what is supported and what
is not. Additional <literal>InnoDB</literal>-specific information
about replication is given in
- <xref linkend="innodb-and-mysql-replication"/>.
- Replication issues with regard to stored routines and triggers is
- described in <xref linkend="stored-procedure-logging"/>.
+ <xref linkend="innodb-and-mysql-replication"/>. Replication issues
+ with regard to stored routines and triggers is described in
+ <xref linkend="stored-procedure-logging"/>.
</para>
<itemizedlist>
@@ -1855,14 +1855,14 @@
</para></listitem>
<listitem><para>
- For both master and slave the same system time zone
- should be set. Otherwise some statements, for example statements
- using <literal>NOW()</literal> or <literal>FROM_UNIXTIME()</literal>
- functions, won't be replicated properly. One could set the time zone in
- which MySQL server runs by using the
- <literal>--timezone=<replaceable>timezone_name</replaceable></literal>
- option of the <filename>mysqld_safe</filename> script or by setting the
- <literal>TZ</literal> environment variable. Also starting from
+ For both master and slave the same system time zone should be set.
+ Otherwise some statements, for example statements using
+ <literal>NOW()</literal> or <literal>FROM_UNIXTIME()</literal>
+ functions, won't be replicated properly. One could set the time zone
+ in which MySQL server runs by using the
+ <literal>--timezone=<replaceable>timezone_name</replaceable></literal>
+ option of the <filename>mysqld_safe</filename> script or by setting
+ the <literal>TZ</literal> environment variable. Also starting from
version 4.1.3 both master and slave should have the same default
connection time zone set, that is the
<literal>--default-time-zone</literal> parameter should have the
--- 1.4/refman-5.0/triggers.xml 2005-07-08 09:35:43 -05:00
+++ 1.5/refman-5.0/triggers.xml 2005-07-08 09:38:03 -05:00
@@ -35,10 +35,10 @@
and show some examples of how to use them.
</para>
- <para>
- Binary logging for triggers is done as described in
- <xref linkend="stored-procedure-logging"/>.
- </para>
+ <para>
+ Binary logging for triggers is done as described in
+ <xref linkend="stored-procedure-logging"/>.
+ </para>
<section id="create-trigger">
@@ -105,8 +105,8 @@
<para>
<emphasis role="bold">Note</emphasis>: Currently, triggers are not
- activated by cascaded foreign key actions. This limitation will be lifted
- as soon as possible.
+ activated by cascaded foreign key actions. This limitation will be
+ lifted as soon as possible.
</para>
<para>
--- 1.3/refman/replication.xml 2005-07-08 09:35:44 -05:00
+++ 1.4/refman/replication.xml 2005-07-08 09:38:03 -05:00
@@ -1760,9 +1760,9 @@
The following list provides details about what is supported and what
is not. Additional <literal>InnoDB</literal>-specific information
about replication is given in
- <xref linkend="innodb-and-mysql-replication"/>.
- Replication issues with regard to stored routines and triggers is
- described in <xref linkend="stored-procedure-logging"/>.
+ <xref linkend="innodb-and-mysql-replication"/>. Replication issues
+ with regard to stored routines and triggers is described in
+ <xref linkend="stored-procedure-logging"/>.
</para>
<itemizedlist>
@@ -1855,14 +1855,14 @@
</para></listitem>
<listitem><para>
- For both master and slave the same system time zone
- should be set. Otherwise some statements, for example statements
- using <literal>NOW()</literal> or <literal>FROM_UNIXTIME()</literal>
- functions, won't be replicated properly. One could set the time zone in
- which MySQL server runs by using the
- <literal>--timezone=<replaceable>timezone_name</replaceable></literal>
- option of the <filename>mysqld_safe</filename> script or by setting the
- <literal>TZ</literal> environment variable. Also starting from
+ For both master and slave the same system time zone should be set.
+ Otherwise some statements, for example statements using
+ <literal>NOW()</literal> or <literal>FROM_UNIXTIME()</literal>
+ functions, won't be replicated properly. One could set the time zone
+ in which MySQL server runs by using the
+ <literal>--timezone=<replaceable>timezone_name</replaceable></literal>
+ option of the <filename>mysqld_safe</filename> script or by setting
+ the <literal>TZ</literal> environment variable. Also starting from
version 4.1.3 both master and slave should have the same default
connection time zone set, that is the
<literal>--default-time-zone</literal> parameter should have the
--- 1.4/refman/triggers.xml 2005-07-08 09:35:45 -05:00
+++ 1.5/refman/triggers.xml 2005-07-08 09:38:04 -05:00
@@ -35,10 +35,10 @@
and show some examples of how to use them.
</para>
- <para>
- Binary logging for triggers is done as described in
- <xref linkend="stored-procedure-logging"/>.
- </para>
+ <para>
+ Binary logging for triggers is done as described in
+ <xref linkend="stored-procedure-logging"/>.
+ </para>
<section id="create-trigger">
@@ -105,8 +105,8 @@
<para>
<emphasis role="bold">Note</emphasis>: Currently, triggers are not
- activated by cascaded foreign key actions. This limitation will be lifted
- as soon as possible.
+ activated by cascaded foreign key actions. This limitation will be
+ lifted as soon as possible.
</para>
<para>
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (paul:1.2961) | paul | 11 Jul |
