bk commit - mysqldoc@docsrva tree (paul:1.3107)

[paul]

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.3107 05/07/22 18:48:46 paul@stripped +4 -0
  Mention trigger namespace change explicitly.

  refman/triggers.xml
    1.11 05/07/22 18:48:43 paul@stripped +5 -5
    Tweak.

  refman/news.xml
    1.95 05/07/22 18:48:43 paul@stripped +6 -3
    Mention trigger namespace change explicitly.

  refman-5.0/triggers.xml
    1.11 05/07/22 18:48:42 paul@stripped +5 -5
    Sync.

  refman-5.0/news.xml
    1.80 05/07/22 18:48:42 paul@stripped +6 -3
    Sync.

# 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.79/refman-5.0/news.xml	2005-07-22 16:51:01 -05:00
+++ 1.80/refman-5.0/news.xml	2005-07-22 18:48:42 -05:00
@@ -316,9 +316,12 @@
 
         <listitem>
           <para>
-            <literal>DROP TRIGGER</literal> now requires a schema name
-            instead of a table name (schema name is optional and, if
-            omitted, the current schema will be used).
+            The namespace for triggers has changed. Previously, trigger
+            names had to be unique per trigger. Now they must be unique
+            within the schema (database). An implication of this change
+            is that <literal>DROP TRIGGER</literal> syntax now uses a
+            schema name instead of a table name (schema name is optional
+            and, if omitted, the current schema will be used).
           </para>
 
           <para>

--- 1.10/refman-5.0/triggers.xml	2005-07-22 10:36:24 -05:00
+++ 1.11/refman-5.0/triggers.xml	2005-07-22 18:48:42 -05:00
@@ -151,18 +151,18 @@
 <!--  There is no IF EXISTS clause, apparently. -->
 
 <programlisting>
-DROP TRIGGER
[<replaceable>schema</replaceable>.]<replaceable>trigger_name</replaceable>
+DROP TRIGGER
[<replaceable>schema_name</replaceable>.]<replaceable>trigger_name</replaceable>
 </programlisting>
 
     <para>
-      Drops a trigger. The schema is optional. If the schema is omitted,
-      the trigger is dropped from the current schema.
+      Drops a trigger. The schema name is optional. If the schema is
+      omitted, the trigger is dropped from the current schema.
     </para>
 
     <para>
       Prior to MySQL 5.0.10, the table name was required instead of the
-      schema (<literal><replaceable>table_name</replaceable>.xreplace
-      trigger_name</literal>).
+      schema name
+     
(<literal><replaceable>table_name</replaceable>.<replaceable>trigger_name</replaceable></literal>).
     </para>
 
     <para>

--- 1.94/refman/news.xml	2005-07-22 16:51:02 -05:00
+++ 1.95/refman/news.xml	2005-07-22 18:48:43 -05:00
@@ -319,9 +319,12 @@
 
         <listitem>
           <para>
-            <literal>DROP TRIGGER</literal> now requires a schema name
-            instead of a table name (schema name is optional and, if
-            omitted, the current schema will be used).
+            The namespace for triggers has changed. Previously, trigger
+            names had to be unique per trigger. Now they must be unique
+            within the schema (database). An implication of this change
+            is that <literal>DROP TRIGGER</literal> syntax now uses a
+            schema name instead of a table name (schema name is optional
+            and, if omitted, the current schema will be used).
           </para>
 
           <para>

--- 1.10/refman/triggers.xml	2005-07-22 10:36:23 -05:00
+++ 1.11/refman/triggers.xml	2005-07-22 18:48:43 -05:00
@@ -151,18 +151,18 @@
 <!--  There is no IF EXISTS clause, apparently. -->
 
 <programlisting>
-DROP TRIGGER
[<replaceable>schema</replaceable>.]<replaceable>trigger_name</replaceable>
+DROP TRIGGER
[<replaceable>schema_name</replaceable>.]<replaceable>trigger_name</replaceable>
 </programlisting>
 
     <para>
-      Drops a trigger. The schema is optional. If the schema is omitted,
-      the trigger is dropped from the current schema.
+      Drops a trigger. The schema name is optional. If the schema is
+      omitted, the trigger is dropped from the current schema.
     </para>
 
     <para>
       Prior to MySQL 5.0.10, the table name was required instead of the
-      schema (<literal><replaceable>table_name</replaceable>.xreplace
-      trigger_name</literal>).
+      schema name
+     
(<literal><replaceable>table_name</replaceable>.<replaceable>trigger_name</replaceable></literal>).
     </para>
 
     <para>