Author: paul
Date: 2008-03-18 17:49:20 +0100 (Tue, 18 Mar 2008)
New Revision: 10291
Log:
r30260@arctic: paul | 2008-03-18 10:15:15 -0500
Say how to upgrade events table.
An event restriction should say stored functions, not stored routines.
Modified:
trunk/it/refman-5.1/events.xml
trunk/pt/refman-5.1/events.xml
trunk/refman-5.1/events.xml
trunk/refman-6.0/events.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:30089
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:30241
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:30089
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:30260
Modified: trunk/it/refman-5.1/events.xml
===================================================================
--- trunk/it/refman-5.1/events.xml 2008-03-18 16:49:14 UTC (rev 10290)
+++ trunk/it/refman-5.1/events.xml 2008-03-18 16:49:20 UTC (rev 10291)
Changed blocks: 3, Lines Added: 6, Lines Deleted: 4; 2049 bytes
@@ -1143,7 +1143,9 @@
Due to this change, the <literal>mysql.event</literal>
table must be updated before events created in earlier
releases can be created, altered, viewed, or used in MySQL
- 5.1.17 or later.
+ 5.1.17 or later. You can use
+ <command>mysql_upgrade</command> for this (see
+ <xref linkend="mysql-upgrade"/>).
</para>
<para>
@@ -1161,12 +1163,12 @@
involving built-in MySQL functions and user variables to obtain
any of the <replaceable>timestamp</replaceable> or
<replaceable>interval</replaceable> values which it contains.
- You may not use stored routines or user-defined functions in
+ You may not use stored functions or user-defined functions in
such expressions, nor may you use any table references; however,
you may use <literal>SELECT FROM DUAL</literal>. This is true
for both <literal>CREATE EVENT</literal> and <literal>ALTER
EVENT</literal> statements. Beginning with MySQL 5.1.13,
- references to stored routines, user-defined functions, and
+ references to stored functions, user-defined functions, and
tables in such cases are specifically disallowed, and fail with
an error (see Bug #22830).
</para>
@@ -2112,7 +2114,7 @@
<title>Database object references in <literal>ON SCHEDULE</literal> clauses</title>
<para>
- References to stored routines, user-defined functions, and
+ References to stored functions, user-defined functions, and
tables in the <literal>ON SCHEDULE</literal> clauses of
<literal>CREATE EVENT</literal> and <literal>ALTER
EVENT</literal> statements are not supported. Beginning with
Modified: trunk/pt/refman-5.1/events.xml
===================================================================
--- trunk/pt/refman-5.1/events.xml 2008-03-18 16:49:14 UTC (rev 10290)
+++ trunk/pt/refman-5.1/events.xml 2008-03-18 16:49:20 UTC (rev 10291)
Changed blocks: 3, Lines Added: 6, Lines Deleted: 4; 2049 bytes
@@ -1143,7 +1143,9 @@
Due to this change, the <literal>mysql.event</literal>
table must be updated before events created in earlier
releases can be created, altered, viewed, or used in MySQL
- 5.1.17 or later.
+ 5.1.17 or later. You can use
+ <command>mysql_upgrade</command> for this (see
+ <xref linkend="mysql-upgrade"/>).
</para>
<para>
@@ -1161,12 +1163,12 @@
involving built-in MySQL functions and user variables to obtain
any of the <replaceable>timestamp</replaceable> or
<replaceable>interval</replaceable> values which it contains.
- You may not use stored routines or user-defined functions in
+ You may not use stored functions or user-defined functions in
such expressions, nor may you use any table references; however,
you may use <literal>SELECT FROM DUAL</literal>. This is true
for both <literal>CREATE EVENT</literal> and <literal>ALTER
EVENT</literal> statements. Beginning with MySQL 5.1.13,
- references to stored routines, user-defined functions, and
+ references to stored functions, user-defined functions, and
tables in such cases are specifically disallowed, and fail with
an error (see Bug #22830).
</para>
@@ -2112,7 +2114,7 @@
<title>Database object references in <literal>ON SCHEDULE</literal> clauses</title>
<para>
- References to stored routines, user-defined functions, and
+ References to stored functions, user-defined functions, and
tables in the <literal>ON SCHEDULE</literal> clauses of
<literal>CREATE EVENT</literal> and <literal>ALTER
EVENT</literal> statements are not supported. Beginning with
Modified: trunk/refman-5.1/events.xml
===================================================================
--- trunk/refman-5.1/events.xml 2008-03-18 16:49:14 UTC (rev 10290)
+++ trunk/refman-5.1/events.xml 2008-03-18 16:49:20 UTC (rev 10291)
Changed blocks: 3, Lines Added: 6, Lines Deleted: 4; 2040 bytes
@@ -1140,7 +1140,9 @@
Due to this change, the <literal>mysql.event</literal>
table must be updated before events created in earlier
releases can be created, altered, viewed, or used in MySQL
- 5.1.17 or later.
+ 5.1.17 or later. You can use
+ <command>mysql_upgrade</command> for this (see
+ <xref linkend="mysql-upgrade"/>).
</para>
<para>
@@ -1158,12 +1160,12 @@
involving built-in MySQL functions and user variables to obtain
any of the <replaceable>timestamp</replaceable> or
<replaceable>interval</replaceable> values which it contains.
- You may not use stored routines or user-defined functions in
+ You may not use stored functions or user-defined functions in
such expressions, nor may you use any table references; however,
you may use <literal>SELECT FROM DUAL</literal>. This is true
for both <literal>CREATE EVENT</literal> and <literal>ALTER
EVENT</literal> statements. Beginning with MySQL 5.1.13,
- references to stored routines, user-defined functions, and
+ references to stored functions, user-defined functions, and
tables in such cases are specifically disallowed, and fail with
an error (see Bug #22830).
</para>
@@ -2109,7 +2111,7 @@
<title>Database object references in <literal>ON SCHEDULE</literal> clauses</title>
<para>
- References to stored routines, user-defined functions, and
+ References to stored functions, user-defined functions, and
tables in the <literal>ON SCHEDULE</literal> clauses of
<literal>CREATE EVENT</literal> and <literal>ALTER
EVENT</literal> statements are not supported. Beginning with
Modified: trunk/refman-6.0/events.xml
===================================================================
--- trunk/refman-6.0/events.xml 2008-03-18 16:49:14 UTC (rev 10290)
+++ trunk/refman-6.0/events.xml 2008-03-18 16:49:20 UTC (rev 10291)
Changed blocks: 3, Lines Added: 5, Lines Deleted: 5; 2392 bytes
@@ -634,11 +634,11 @@
involving built-in MySQL functions and user variables to obtain
any of the <replaceable>timestamp</replaceable> or
<replaceable>interval</replaceable> values which it contains.
- You may not use stored routines or user-defined functions in
+ You may not use stored functions or user-defined functions in
such expressions, nor may you use any table references; however,
you may use <literal>SELECT FROM DUAL</literal>. This is true
for both <literal>ALTER EVENT</literal> and <literal>CREATE
- EVENT</literal> statements. References to stored routines,
+ EVENT</literal> statements. References to stored functions,
user-defined functions, and tables in such cases are
specifically disallowed, and fail with an error (see Bug
#22830).
@@ -1075,11 +1075,11 @@
involving built-in MySQL functions and user variables to obtain
any of the <replaceable>timestamp</replaceable> or
<replaceable>interval</replaceable> values which it contains.
- You may not use stored routines or user-defined functions in
+ You may not use stored functions or user-defined functions in
such expressions, nor may you use any table references; however,
you may use <literal>SELECT FROM DUAL</literal>. This is true
for both <literal>CREATE EVENT</literal> and <literal>ALTER
- EVENT</literal> statements. References to stored routines,
+ EVENT</literal> statements. References to stored functions,
user-defined functions, and tables in such cases are
specifically disallowed, and fail with an error (see Bug
#22830).
@@ -1923,7 +1923,7 @@
<title>Database object references in <literal>ON SCHEDULE</literal> clauses</title>
<para>
- References to stored routines, user-defined functions, and
+ References to stored functions, user-defined functions, and
tables in the <literal>ON SCHEDULE</literal> clauses of
<literal>CREATE EVENT</literal> and <literal>ALTER
EVENT</literal> statements are not supported. These sorts of
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10291 - in trunk: . it/refman-5.1 pt/refman-5.1 refman-5.1 refman-6.0 | paul | 18 Mar |
