| List: | Commits | « Previous MessageNext Message » | |
| From: | paul | Date: | May 8 2008 6:55pm |
| Subject: | svn commit - mysqldoc@docsrva: r10695 - in trunk: . it/refman-5.1 pt/refman-5.1 refman-5.1 refman-6.0 | ||
| View as plain text | |||
Author: paul Date: 2008-05-08 18:55:40 +0200 (Thu, 08 May 2008) New Revision: 10695 Log: r31252@frost: paul | 2008-05-08 11:44:46 -0500 events: general revisions 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:31251 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31182 + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:31252 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31182 Modified: trunk/it/refman-5.1/events.xml =================================================================== --- trunk/it/refman-5.1/events.xml 2008-05-08 16:55:30 UTC (rev 10694) +++ trunk/it/refman-5.1/events.xml 2008-05-08 16:55:40 UTC (rev 10695) Changed blocks: 6, Lines Added: 11, Lines Deleted: 11; 2388 bytes @@ -1437,7 +1437,7 @@ <listitem> <para> - Querying the <literal>EVENTS</literal> table of the + Query the <literal>EVENTS</literal> table of the <literal>INFORMATION_SCHEMA</literal> database. See <xref linkend="events-table"/>. </para> @@ -1445,14 +1445,14 @@ <listitem> <para> - Using the <literal>SHOW EVENTS</literal> statement. See + Use the <literal>SHOW EVENTS</literal> statement. See <xref linkend="show-events"/>. </para> </listitem> <listitem> <para> - Using the <literal>SHOW CREATE EVENT</literal> statement. See + Use the <literal>SHOW CREATE EVENT</literal> statement. See <xref linkend="show-create-event"/>. </para> </listitem> @@ -1460,8 +1460,8 @@ <listitem> <para> A record of events executed on the server can be read from the - MySQL Server's error log (see - <xref linkend="events-privileges"/> for an example). + MySQL Server's error log. See + <xref linkend="events-privileges"/> for an example. </para> </listitem> @@ -1587,7 +1587,7 @@ <para> To grant this same user the <literal>EVENT</literal> privilege on - all schemas would require the following statement: + all schemas, use the following statement: </para> <programlisting> @@ -1595,9 +1595,9 @@ </programlisting> <para> - The <literal>EVENT</literal> privilege has schema-level scope. - Therefore, trying to grant it on a single table results in an - error as shown: + The <literal>EVENT</literal> privilege has global or schema-level + scope. Therefore, trying to grant it on a single table results in + an error as shown: </para> <programlisting> @@ -1733,8 +1733,8 @@ </para> <para> - An event is not migrated or dropped as a result of the renaming - or dropping of the user who created it. + An event is not migrated or dropped as a result of renaming or + dropping the user who created it. </para> </important> Modified: trunk/pt/refman-5.1/events.xml =================================================================== --- trunk/pt/refman-5.1/events.xml 2008-05-08 16:55:30 UTC (rev 10694) +++ trunk/pt/refman-5.1/events.xml 2008-05-08 16:55:40 UTC (rev 10695) Changed blocks: 6, Lines Added: 11, Lines Deleted: 11; 2388 bytes @@ -1437,7 +1437,7 @@ <listitem> <para> - Querying the <literal>EVENTS</literal> table of the + Query the <literal>EVENTS</literal> table of the <literal>INFORMATION_SCHEMA</literal> database. See <xref linkend="events-table"/>. </para> @@ -1445,14 +1445,14 @@ <listitem> <para> - Using the <literal>SHOW EVENTS</literal> statement. See + Use the <literal>SHOW EVENTS</literal> statement. See <xref linkend="show-events"/>. </para> </listitem> <listitem> <para> - Using the <literal>SHOW CREATE EVENT</literal> statement. See + Use the <literal>SHOW CREATE EVENT</literal> statement. See <xref linkend="show-create-event"/>. </para> </listitem> @@ -1460,8 +1460,8 @@ <listitem> <para> A record of events executed on the server can be read from the - MySQL Server's error log (see - <xref linkend="events-privileges"/> for an example). + MySQL Server's error log. See + <xref linkend="events-privileges"/> for an example. </para> </listitem> @@ -1587,7 +1587,7 @@ <para> To grant this same user the <literal>EVENT</literal> privilege on - all schemas would require the following statement: + all schemas, use the following statement: </para> <programlisting> @@ -1595,9 +1595,9 @@ </programlisting> <para> - The <literal>EVENT</literal> privilege has schema-level scope. - Therefore, trying to grant it on a single table results in an - error as shown: + The <literal>EVENT</literal> privilege has global or schema-level + scope. Therefore, trying to grant it on a single table results in + an error as shown: </para> <programlisting> @@ -1733,8 +1733,8 @@ </para> <para> - An event is not migrated or dropped as a result of the renaming - or dropping of the user who created it. + An event is not migrated or dropped as a result of renaming or + dropping the user who created it. </para> </important> Modified: trunk/refman-5.1/events.xml =================================================================== --- trunk/refman-5.1/events.xml 2008-05-08 16:55:30 UTC (rev 10694) +++ trunk/refman-5.1/events.xml 2008-05-08 16:55:40 UTC (rev 10695) Changed blocks: 6, Lines Added: 11, Lines Deleted: 11; 2379 bytes @@ -1437,7 +1437,7 @@ <listitem> <para> - Querying the <literal>EVENTS</literal> table of the + Query the <literal>EVENTS</literal> table of the <literal>INFORMATION_SCHEMA</literal> database. See <xref linkend="events-table"/>. </para> @@ -1445,14 +1445,14 @@ <listitem> <para> - Using the <literal>SHOW EVENTS</literal> statement. See + Use the <literal>SHOW EVENTS</literal> statement. See <xref linkend="show-events"/>. </para> </listitem> <listitem> <para> - Using the <literal>SHOW CREATE EVENT</literal> statement. See + Use the <literal>SHOW CREATE EVENT</literal> statement. See <xref linkend="show-create-event"/>. </para> </listitem> @@ -1460,8 +1460,8 @@ <listitem> <para> A record of events executed on the server can be read from the - MySQL Server's error log (see - <xref linkend="events-privileges"/> for an example). + MySQL Server's error log. See + <xref linkend="events-privileges"/> for an example. </para> </listitem> @@ -1587,7 +1587,7 @@ <para> To grant this same user the <literal>EVENT</literal> privilege on - all schemas would require the following statement: + all schemas, use the following statement: </para> <programlisting> @@ -1595,9 +1595,9 @@ </programlisting> <para> - The <literal>EVENT</literal> privilege has schema-level scope. - Therefore, trying to grant it on a single table results in an - error as shown: + The <literal>EVENT</literal> privilege has global or schema-level + scope. Therefore, trying to grant it on a single table results in + an error as shown: </para> <programlisting> @@ -1733,8 +1733,8 @@ </para> <para> - An event is not migrated or dropped as a result of the renaming - or dropping of the user who created it. + An event is not migrated or dropped as a result of renaming or + dropping the user who created it. </para> </important> Modified: trunk/refman-6.0/events.xml =================================================================== --- trunk/refman-6.0/events.xml 2008-05-08 16:55:30 UTC (rev 10694) +++ trunk/refman-6.0/events.xml 2008-05-08 16:55:40 UTC (rev 10695) Changed blocks: 6, Lines Added: 11, Lines Deleted: 11; 2379 bytes @@ -1344,7 +1344,7 @@ <listitem> <para> - Querying the <literal>EVENTS</literal> table of the + Query the <literal>EVENTS</literal> table of the <literal>INFORMATION_SCHEMA</literal> database. See <xref linkend="events-table"/>. </para> @@ -1352,14 +1352,14 @@ <listitem> <para> - Using the <literal>SHOW EVENTS</literal> statement. See + Use the <literal>SHOW EVENTS</literal> statement. See <xref linkend="show-events"/>. </para> </listitem> <listitem> <para> - Using the <literal>SHOW CREATE EVENT</literal> statement. See + Use the <literal>SHOW CREATE EVENT</literal> statement. See <xref linkend="show-create-event"/>. </para> </listitem> @@ -1367,8 +1367,8 @@ <listitem> <para> A record of events executed on the server can be read from the - MySQL Server's error log (see - <xref linkend="events-privileges"/> for an example). + MySQL Server's error log. See + <xref linkend="events-privileges"/> for an example. </para> </listitem> @@ -1467,7 +1467,7 @@ <para> To grant this same user the <literal>EVENT</literal> privilege on - all schemas would require the following statement: + all schemas, use the following statement: </para> <programlisting> @@ -1475,9 +1475,9 @@ </programlisting> <para> - The <literal>EVENT</literal> privilege has schema-level scope. - Therefore, trying to grant it on a single table results in an - error as shown: + The <literal>EVENT</literal> privilege has global or schema-level + scope. Therefore, trying to grant it on a single table results in + an error as shown: </para> <programlisting> @@ -1603,8 +1603,8 @@ </para> <para> - An event is not migrated or dropped as a result of the renaming - or dropping of the user who created it. + An event is not migrated or dropped as a result of renaming or + dropping the user who created it. </para> </important>
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r10695 - in trunk: . it/refman-5.1 pt/refman-5.1 refman-5.1 refman-6.0 | paul | 8 May 2008 |
© 1995-2008 MySQL AB. All rights reserved.
Page generated in 0.397 sec. using MySQL 5.1.14-beta-log