svn commit - mysqldoc@docsrva: r10361 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-5.2 refman-6.0 refman-common

[mcbrown]

Author: mcbrown
Date: 2008-03-28 15:07:52 +0100 (Fri, 28 Mar 2008)
New Revision: 10361

Log:
Quick fix for proxy docs



Modified:
   trunk/refman-4.1/renamed-nodes.txt
   trunk/refman-5.0/renamed-nodes.txt
   trunk/refman-5.1/renamed-nodes.txt
   trunk/refman-5.2/renamed-nodes.txt
   trunk/refman-6.0/renamed-nodes.txt
   trunk/refman-common/mysql-proxy.xml


Modified: trunk/refman-4.1/renamed-nodes.txt
===================================================================
--- trunk/refman-4.1/renamed-nodes.txt	2008-03-27 22:34:35 UTC (rev 10360)
+++ trunk/refman-4.1/renamed-nodes.txt	2008-03-28 14:07:52 UTC (rev 10361)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 504 bytes

@@ -328,3 +328,4 @@
 year-2000-compliance y2k-issues
 disaster-prevention backup-and-recovery 2009-03-01
 backup-recovery recovery-from-backups 2009-03-01
+mysql-proxy-scripting-structures-servers mysql-proxy-scripting-structures-backends
2009-03-28


Modified: trunk/refman-5.0/renamed-nodes.txt
===================================================================
--- trunk/refman-5.0/renamed-nodes.txt	2008-03-27 22:34:35 UTC (rev 10360)
+++ trunk/refman-5.0/renamed-nodes.txt	2008-03-28 14:07:52 UTC (rev 10361)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 519 bytes

@@ -663,3 +663,4 @@
 using-mysql-programs programs-using 2009-01-01
 disaster-prevention backup-and-recovery 2009-03-01
 backup-recovery recovery-from-backups 2009-03-01
+mysql-proxy-scripting-structures-servers mysql-proxy-scripting-structures-backends
2009-03-28


Modified: trunk/refman-5.1/renamed-nodes.txt
===================================================================
--- trunk/refman-5.1/renamed-nodes.txt	2008-03-27 22:34:35 UTC (rev 10360)
+++ trunk/refman-5.1/renamed-nodes.txt	2008-03-28 14:07:52 UTC (rev 10361)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 559 bytes

@@ -432,3 +432,4 @@
 disaster-prevention backup-and-recovery 2009-03-01
 backup-recovery recovery-from-backups 2009-03-01
 mysql-tableinfo http://dev.mysql.com/doc/refman/5.0/en/mysql-tableinfo.html 2009-03-18
+mysql-proxy-scripting-structures-servers mysql-proxy-scripting-structures-backends
2009-03-28


Modified: trunk/refman-5.2/renamed-nodes.txt
===================================================================
--- trunk/refman-5.2/renamed-nodes.txt	2008-03-27 22:34:35 UTC (rev 10360)
+++ trunk/refman-5.2/renamed-nodes.txt	2008-03-28 14:07:52 UTC (rev 10361)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 599 bytes

@@ -3771,3 +3771,4 @@
 xml-functions	http://dev.mysql.com/doc/refman/6.0/en/xml-functions.html 2008-03-31
 y2k-issues	http://dev.mysql.com/doc/refman/6.0/en/y2k-issues.html 2008-03-31
 year	http://dev.mysql.com/doc/refman/6.0/en/year.html 2008-03-31
+mysql-proxy-scripting-structures-servers mysql-proxy-scripting-structures-backends
2009-03-28


Modified: trunk/refman-6.0/renamed-nodes.txt
===================================================================
--- trunk/refman-6.0/renamed-nodes.txt	2008-03-27 22:34:35 UTC (rev 10360)
+++ trunk/refman-6.0/renamed-nodes.txt	2008-03-28 14:07:52 UTC (rev 10361)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 557 bytes

@@ -58,3 +58,4 @@
 disaster-prevention backup-and-recovery 2009-03-01
 backup-recovery recovery-from-backups 2009-03-01
 mysql-tableinfo http://dev.mysql.com/doc/refman/5.0/en/mysql-tableinfo.html 2009-03-18
+mysql-proxy-scripting-structures-servers mysql-proxy-scripting-structures-backends
2009-03-28


Modified: trunk/refman-common/mysql-proxy.xml
===================================================================
--- trunk/refman-common/mysql-proxy.xml	2008-03-27 22:34:35 UTC (rev 10360)
+++ trunk/refman-common/mysql-proxy.xml	2008-03-28 14:07:52 UTC (rev 10361)
Changed blocks: 4, Lines Added: 9, Lines Deleted: 9; 2748 bytes

@@ -900,8 +900,8 @@
               <entry>A structure containing the list of configured backend servers.
For a
                 list of attributes, see
                 <link
-                  linkend="mysql-proxy-scripting-structures-servers">
-                <literal>proxy.servers</literal> </link>.</entry>
+                  linkend="mysql-proxy-scripting-structures-backends">
+                <literal>proxy.backends</literal>
</link>.</entry>
             </row>
             <row>
               <entry><literal>queries</literal></entry>

@@ -954,19 +954,19 @@
               <entry><literal>backend_ndx</literal></entry>
               <entry>The ID of the server used for this connection. This is an ID
valid
                 against the list of configured servers available through
-                the <literal>proxy.servers</literal> object.</entry>
+                the <literal>proxy.backends</literal> object.</entry>
             </row>
           </tbody>
         </tgroup>
       </informaltable>
 
-      <para id="mysql-proxy-scripting-structures-servers">
-        <emphasis role="bold"> <literal>proxy.servers</literal>
+      <para id="mysql-proxy-scripting-structures-backends">
+        <emphasis role="bold"> <literal>proxy.backends</literal>
         </emphasis>
       </para>
 
       <para>
-        The <literal>proxy.servers</literal> table is partially writable
+        The <literal>proxy.backends</literal> table is partially writable
         and contains an array of all the configured backend servers and
         the server metadata (IP address, status, etc.). You can
         determine the array index of the current connection using

@@ -977,7 +977,7 @@
 
       <para>
         The attributes for each entry within the
-        <literal>proxy.servers</literal> table are shown in this table.
+        <literal>proxy.backends</literal> table are shown in this table.
       </para>
 
       <informaltable>

@@ -1538,13 +1538,13 @@
                 proxy.connection.backend_ndx = 1
                 print("Choosing backend 1")
         end
-        print("Using " .. proxy.servers[proxy.connection.backend_ndx].address)
+        print("Using " .. proxy.backends[proxy.connection.backend_ndx].address)
 end</programlisting>
 
       <para>
         In this example the IP address/port combination is also
         displayed by accessing the information from the internal
-        <literal>proxy.servers</literal> table.
+        <literal>proxy.backends</literal> table.
       </para>
 
     </section>