List:Commits« Previous MessageNext Message »
From:paul.dubois Date:May 17 2010 6:39pm
Subject:svn commit - mysqldoc@docsrva: r20673 - in trunk: . refman-5.0 refman-5.1 refman-5.4 refman-5.5 refman-6.0
View as plain text  
Author: paul
Date: 2010-05-17 20:39:14 +0200 (Mon, 17 May 2010)
New Revision: 20673

Log:
 r59052@frost:  paul | 2010-05-17 13:38:23 -0500
 Revise description of nonexistent DEFINER at object execution time


Modified:
   trunk/refman-5.0/sql-syntax-data-definition.xml
   trunk/refman-5.1/sql-syntax-data-definition.xml
   trunk/refman-5.4/sql-syntax-data-definition.xml
   trunk/refman-5.5/sql-syntax-data-definition.xml
   trunk/refman-6.0/sql-syntax-data-definition.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:39162
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:59050
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
   + 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:39162
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:59052
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546


Modified: trunk/refman-5.0/sql-syntax-data-definition.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-data-definition.xml	2010-05-17 16:57:04 UTC (rev 20672)
+++ trunk/refman-5.0/sql-syntax-data-definition.xml	2010-05-17 18:39:14 UTC (rev 20673)
Changed blocks: 3, Lines Added: 13, Lines Deleted: 10; 2131 bytes

@@ -2394,10 +2394,11 @@
 
       <listitem>
         <para>
-          Although it is possible to create routines with a nonexistent
-          <literal>DEFINER</literal> value, an error occurs if the
-          routine executes with definer privileges but the definer does
-          not exist at execution time.
+          Although it is possible to create a routine with a nonexistent
+          <literal>DEFINER</literal> account, an error occurs at routine
+          execution time if the <literal>SQL SECURITY</literal> value is
+          <literal>DEFINER</literal> but the definer account does not
+          exist.
         </para>
       </listitem>
 

@@ -4582,9 +4583,9 @@
 
       <listitem>
         <para>
-          Although it is possible to create triggers with a nonexistent
-          <literal>DEFINER</literal> value, it is not a good idea for
-          such triggers to be activated until the definer actually does
+          Although it is possible to create a trigger with a nonexistent
+          <literal>DEFINER</literal> account, it is not a good idea for
+          such triggers to be activated until the account actually does
           exist. Otherwise, the behavior with respect to privilege
           checking is undefined.
         </para>

@@ -5213,9 +5214,11 @@
 
       <listitem>
         <para>
-          If the <literal>SQL SECURITY</literal> value is
-          <literal>DEFINER</literal> but the definer account does not
-          exist when the view is referenced, an error occurs.
+          Although it is possible to create a view with a nonexistent
+          <literal>DEFINER</literal> account, an error occurs when the
+          view is referenced if the <literal>SQL SECURITY</literal>
+          value is <literal>DEFINER</literal> but the definer account
+          does not exist.
         </para>
       </listitem>
 


Modified: trunk/refman-5.1/sql-syntax-data-definition.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-data-definition.xml	2010-05-17 16:57:04 UTC (rev 20672)
+++ trunk/refman-5.1/sql-syntax-data-definition.xml	2010-05-17 18:39:14 UTC (rev 20673)
Changed blocks: 4, Lines Added: 16, Lines Deleted: 14; 2666 bytes

@@ -3256,10 +3256,9 @@
 
       <listitem>
         <para>
-          Although it is possible to create events with a nonexistent
-          <literal>DEFINER</literal> value, an error occurs if the event
-          executes with definer privileges but the definer does not
-          exist at execution time.
+          Although it is possible to create an event with a nonexistent
+          <literal>DEFINER</literal> account, an error occurs at event
+          execution time if the account does not exist.
         </para>
       </listitem>
 

@@ -4860,10 +4859,11 @@
 
       <listitem>
         <para>
-          Although it is possible to create routines with a nonexistent
-          <literal>DEFINER</literal> value, an error occurs if the
-          routine executes with definer privileges but the definer does
-          not exist at execution time.
+          Although it is possible to create a routine with a nonexistent
+          <literal>DEFINER</literal> account, an error occurs at routine
+          execution time if the <literal>SQL SECURITY</literal> value is
+          <literal>DEFINER</literal> but the definer account does not
+          exist.
         </para>
       </listitem>
 

@@ -8155,9 +8155,9 @@
 
       <listitem>
         <para>
-          Although it is possible to create triggers with a nonexistent
-          <literal>DEFINER</literal> value, it is not a good idea for
-          such triggers to be activated until the definer actually does
+          Although it is possible to create a trigger with a nonexistent
+          <literal>DEFINER</literal> account, it is not a good idea for
+          such triggers to be activated until the account actually does
           exist. Otherwise, the behavior with respect to privilege
           checking is undefined.
         </para>

@@ -8751,9 +8751,11 @@
 
       <listitem>
         <para>
-          If the <literal>SQL SECURITY</literal> value is
-          <literal>DEFINER</literal> but the definer account does not
-          exist when the view is referenced, an error occurs.
+          Although it is possible to create a view with a nonexistent
+          <literal>DEFINER</literal> account, an error occurs when the
+          view is referenced if the <literal>SQL SECURITY</literal>
+          value is <literal>DEFINER</literal> but the definer account
+          does not exist.
         </para>
       </listitem>
 


Modified: trunk/refman-5.4/sql-syntax-data-definition.xml
===================================================================
--- trunk/refman-5.4/sql-syntax-data-definition.xml	2010-05-17 16:57:04 UTC (rev 20672)
+++ trunk/refman-5.4/sql-syntax-data-definition.xml	2010-05-17 18:39:14 UTC (rev 20673)
Changed blocks: 4, Lines Added: 16, Lines Deleted: 14; 2666 bytes

@@ -2346,10 +2346,9 @@
 
       <listitem>
         <para>
-          Although it is possible to create events with a nonexistent
-          <literal>DEFINER</literal> value, an error occurs if the event
-          executes with definer privileges but the definer does not
-          exist at execution time.
+          Although it is possible to create an event with a nonexistent
+          <literal>DEFINER</literal> account, an error occurs at event
+          execution time if the account does not exist.
         </para>
       </listitem>
 

@@ -3722,10 +3721,11 @@
 
       <listitem>
         <para>
-          Although it is possible to create routines with a nonexistent
-          <literal>DEFINER</literal> value, an error occurs if the
-          routine executes with definer privileges but the definer does
-          not exist at execution time.
+          Although it is possible to create a routine with a nonexistent
+          <literal>DEFINER</literal> account, an error occurs at routine
+          execution time if the <literal>SQL SECURITY</literal> value is
+          <literal>DEFINER</literal> but the definer account does not
+          exist.
         </para>
       </listitem>
 

@@ -6586,9 +6586,9 @@
 
       <listitem>
         <para>
-          Although it is possible to create triggers with a nonexistent
-          <literal>DEFINER</literal> value, it is not a good idea for
-          such triggers to be activated until the definer actually does
+          Although it is possible to create a trigger with a nonexistent
+          <literal>DEFINER</literal> account, it is not a good idea for
+          such triggers to be activated until the account actually does
           exist. Otherwise, the behavior with respect to privilege
           checking is undefined.
         </para>

@@ -7138,9 +7138,11 @@
 
       <listitem>
         <para>
-          If the <literal>SQL SECURITY</literal> value is
-          <literal>DEFINER</literal> but the definer account does not
-          exist when the view is referenced, an error occurs.
+          Although it is possible to create a view with a nonexistent
+          <literal>DEFINER</literal> account, an error occurs when the
+          view is referenced if the <literal>SQL SECURITY</literal>
+          value is <literal>DEFINER</literal> but the definer account
+          does not exist.
         </para>
       </listitem>
 


Modified: trunk/refman-5.5/sql-syntax-data-definition.xml
===================================================================
--- trunk/refman-5.5/sql-syntax-data-definition.xml	2010-05-17 16:57:04 UTC (rev 20672)
+++ trunk/refman-5.5/sql-syntax-data-definition.xml	2010-05-17 18:39:14 UTC (rev 20673)
Changed blocks: 4, Lines Added: 16, Lines Deleted: 14; 2666 bytes

@@ -2460,10 +2460,9 @@
 
       <listitem>
         <para>
-          Although it is possible to create events with a nonexistent
-          <literal>DEFINER</literal> value, an error occurs if the event
-          executes with definer privileges but the definer does not
-          exist at execution time.
+          Although it is possible to create an event with a nonexistent
+          <literal>DEFINER</literal> account, an error occurs at event
+          execution time if the account does not exist.
         </para>
       </listitem>
 

@@ -3843,10 +3842,11 @@
 
       <listitem>
         <para>
-          Although it is possible to create routines with a nonexistent
-          <literal>DEFINER</literal> value, an error occurs if the
-          routine executes with definer privileges but the definer does
-          not exist at execution time.
+          Although it is possible to create a routine with a nonexistent
+          <literal>DEFINER</literal> account, an error occurs at routine
+          execution time if the <literal>SQL SECURITY</literal> value is
+          <literal>DEFINER</literal> but the definer account does not
+          exist.
         </para>
       </listitem>
 

@@ -6877,9 +6877,9 @@
 
       <listitem>
         <para>
-          Although it is possible to create triggers with a nonexistent
-          <literal>DEFINER</literal> value, it is not a good idea for
-          such triggers to be activated until the definer actually does
+          Although it is possible to create a trigger with a nonexistent
+          <literal>DEFINER</literal> account, it is not a good idea for
+          such triggers to be activated until the account actually does
           exist. Otherwise, the behavior with respect to privilege
           checking is undefined.
         </para>

@@ -7429,9 +7429,11 @@
 
       <listitem>
         <para>
-          If the <literal>SQL SECURITY</literal> value is
-          <literal>DEFINER</literal> but the definer account does not
-          exist when the view is referenced, an error occurs.
+          Although it is possible to create a view with a nonexistent
+          <literal>DEFINER</literal> account, an error occurs when the
+          view is referenced if the <literal>SQL SECURITY</literal>
+          value is <literal>DEFINER</literal> but the definer account
+          does not exist.
         </para>
       </listitem>
 


Modified: trunk/refman-6.0/sql-syntax-data-definition.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-data-definition.xml	2010-05-17 16:57:04 UTC (rev 20672)
+++ trunk/refman-6.0/sql-syntax-data-definition.xml	2010-05-17 18:39:14 UTC (rev 20673)
Changed blocks: 4, Lines Added: 16, Lines Deleted: 14; 2670 bytes

@@ -2392,10 +2392,9 @@
 
       <listitem>
         <para>
-          Although it is possible to create routines with a nonexistent
-          <literal>DEFINER</literal> value, an error occurs if the
-          routine executes with definer privileges but the definer does
-          not exist at execution time.
+          Although it is possible to create an event with a nonexistent
+          <literal>DEFINER</literal> account, an error occurs at event
+          execution time if the account does not exist.
         </para>
       </listitem>
 

@@ -3804,10 +3803,11 @@
 
       <listitem>
         <para>
-          Although it is possible to create routines with a nonexistent
-          <literal>DEFINER</literal> value, an error occurs if the
-          routine executes with definer privileges but the definer does
-          not exist at execution time.
+          Although it is possible to create a routine with a nonexistent
+          <literal>DEFINER</literal> account, an error occurs at routine
+          execution time if the <literal>SQL SECURITY</literal> value is
+          <literal>DEFINER</literal> but the definer account does not
+          exist.
         </para>
       </listitem>
 

@@ -6681,9 +6681,9 @@
 
       <listitem>
         <para>
-          Although it is possible to create triggers with a nonexistent
-          <literal>DEFINER</literal> value, it is not a good idea for
-          such triggers to be activated until the definer actually does
+          Although it is possible to create a trigger with a nonexistent
+          <literal>DEFINER</literal> account, it is not a good idea for
+          such triggers to be activated until the account actually does
           exist. Otherwise, the behavior with respect to privilege
           checking is undefined.
         </para>

@@ -7266,9 +7266,11 @@
 
       <listitem>
         <para>
-          If the <literal>SQL SECURITY</literal> value is
-          <literal>DEFINER</literal> but the definer account does not
-          exist when the view is referenced, an error occurs.
+          Although it is possible to create a view with a nonexistent
+          <literal>DEFINER</literal> account, an error occurs when the
+          view is referenced if the <literal>SQL SECURITY</literal>
+          value is <literal>DEFINER</literal> but the definer account
+          does not exist.
         </para>
       </listitem>
 


Thread
svn commit - mysqldoc@docsrva: r20673 - in trunk: . refman-5.0 refman-5.1 refman-5.4 refman-5.5 refman-6.0paul.dubois17 May