svn commit - mysqldoc@docsrva: r6630 - trunk/refman-5.1

[jon]

Author: jstephens
Date: 2007-06-02 16:29:31 +0200 (Sat, 02 Jun 2007)
New Revision: 6630

Log:

Documented XML Functions bugfixes: Bug #26815, Bug #27898, Bug #28558

Variable usage with XML functions in 5.1.20



Modified:
   trunk/refman-5.1/functions-core.xml
   trunk/refman-5.1/news-5.1.xml


Modified: trunk/refman-5.1/functions-core.xml
===================================================================
--- trunk/refman-5.1/functions-core.xml	2007-06-02 13:19:21 UTC (rev 6629)
+++ trunk/refman-5.1/functions-core.xml	2007-06-02 14:29:31 UTC (rev 6630)
Changed blocks: 1, Lines Added: 45, Lines Deleted: 0; 2081 bytes

@@ -12741,6 +12741,51 @@
       <ulink url="http://forums.mysql.com/list.php?44">MySQL XML User
       Forum</ulink>.
     </para>
+    
+    <para>
+      Beginning with MySQL 5.1.20, user variables in the XPath
+      expressions used with these functions are supported in two forms,
+      whose notations differ according to whether they are weakly or
+      strongly checked:
+      
+      <itemizedlist>
+        <listitem>
+          <formalpara>
+            <title>Weak checking</title>
+            
+            <para>
+              Variables using the syntax
+             
<literal>$@<replaceable>variable_name</replaceable></literal>
+              are not checked. No warnings or errors are issued by the
+              server if a variable has the wrong type or has previously
+              been assigned a value. This also means the user is fully
+              responsible for any typographical errors, since no
+              warnings will be given if (for example)
+              <literal>$@myvairable</literal> is used where
+              <literal>$@myvariable</literal> was intended.
+            </para>
+          </formalpara>
+        </listitem>
+        
+        <listitem>
+          <formalpara>
+            <title>Strong checking</title>
+            
+            <para>
+              Variables using the syntax
+             
<literal>$<replaceable>variable_name</replaceable></literal>
+              can be declared and used with these functions they are
+              called inside stored procedures. Such variables are local
+              to the stored procedure in which they are defined, and are
+              strongly checked for type and value.
+            </para>
+          </formalpara>
+          
+        </listitem>
+      </itemizedlist>
+      
+      (See also Bug #26518.)
+    </para>
 
     <itemizedlist>
 


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-06-02 13:19:21 UTC (rev 6629)
+++ trunk/refman-5.1/news-5.1.xml	2007-06-02 14:29:31 UTC (rev 6630)
Changed blocks: 2, Lines Added: 26, Lines Deleted: 1; 1400 bytes

@@ -73,7 +73,16 @@
     <itemizedlist>
 
       <listitem>
-        <para></para>
+        <para>
+          User variables and stored procedure variables are now
+          supported for use in XPath expressions employed as arguments
+          to the <literal>ExtractValue()</literal> and
+          <literal>UpdateXML()</literal> functions. (Bug #26518) 
+        </para>
+        
+        <para>
+          See <xref linkend="xml-functions"/>, for more information.
+        </para>
       </listitem>
 
     </itemizedlist>

@@ -108,6 +117,22 @@
           scheduled event caused the server to crash. (Bug #28666)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          Following an invalid call to <literal>UpdateXML()</literal>,
+          calling the function again (even if valid) crashed the server.
+          (Bug #27898)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Calling the <literal>UpdateXML()</literal> function using
+          invalid XPath syntax caused memory corruption possibly leading
+          to a crash of the server. (Bug #28558)
+        </para>
+      </listitem>
 
     </itemizedlist>