svn commit - mysqldoc@docsrva: r10165 - in trunk: . it/refman-5.1 pt/refman-5.1 refman-5.1 refman-6.0

[paul]

Author: paul
Date: 2008-03-07 21:45:22 +0100 (Fri, 07 Mar 2008)
New Revision: 10165

Log:
 r29808@frost:  paul | 2008-03-07 14:25:41 -0600
 Remove some unnecessary version numbers.
 Harmonize versions.


Modified:
   trunk/it/refman-5.1/dba-core.xml
   trunk/it/refman-5.1/restrictions.xml
   trunk/it/refman-5.1/sql-syntax.xml
   trunk/pt/refman-5.1/dba-core.xml
   trunk/pt/refman-5.1/restrictions.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:29803
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:29983
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:29808
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:29983


Modified: trunk/it/refman-5.1/dba-core.xml
===================================================================
--- trunk/it/refman-5.1/dba-core.xml	2008-03-07 19:46:28 UTC (rev 10164)
+++ trunk/it/refman-5.1/dba-core.xml	2008-03-07 20:45:22 UTC (rev 10165)
Changed blocks: 1, Lines Added: 24, Lines Deleted: 0; 1371 bytes

@@ -13031,6 +13031,30 @@
 
           <listitem>
             <para>
+              If a statement is logged by row and the client that
+              executed the statement has any temporary tables, then
+              logging by row is used for all subsequent statements
+              (except for those accessing temporary tables) until all
+              temporary tables in use by that client are dropped
+            </para>
+
+            <para>
+              This is true whether or not any temporary tables are
+              actually logged
+            </para>
+
+            <para>
+              Temporary tables cannot be logged using the row-based
+              format; thus, once row-based logging is used, all
+              subsequent statements using that table are unsafe, and we
+              approximate this condition by treating all statements made
+              by that client as unsafe until the client no longer holds
+              any temporary tables
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
               Beginning with MySQL 5.1.23:
 
               <itemizedlist>


Modified: trunk/it/refman-5.1/restrictions.xml
===================================================================
--- trunk/it/refman-5.1/restrictions.xml	2008-03-07 19:46:28 UTC (rev 10164)
+++ trunk/it/refman-5.1/restrictions.xml	2008-03-07 20:45:22 UTC (rev 10165)
Changed blocks: 4, Lines Added: 100, Lines Deleted: 1; 4350 bytes

@@ -14,7 +14,7 @@
 
   <section id="routine-restrictions">
 
-    <title>Restrictions on Stored Routines and Triggers</title>
+    <title>Restrictions on Stored Routines, Triggers, and Events</title>
 
     <indexterm>
       <primary>stored routine restrictions</primary>

@@ -34,6 +34,15 @@
       <secondary>triggers</secondary>
     </indexterm>
 
+    <indexterm>
+      <primary>event restrictions</primary>
+    </indexterm>
+
+    <indexterm>
+      <primary>restrictions</primary>
+      <secondary>events</secondary>
+    </indexterm>
+
     <para>
       Some of the restrictions noted here apply to all stored routines;
       that is, both to stored procedures and stored functions. Some of

@@ -47,6 +56,13 @@
     </para>
 
     <para>
+      All of the restrictions for stored procedures also apply to the
+      <literal>DO</literal> clause of event definitions. For additional
+      event-related restrictions, see
+      <xref linkend="events-limitations-restrictions"/>.
+    </para>
+
+    <para>
       Stored routines cannot contain arbitrary SQL statements. The
       following statements are disallowed:
     </para>

@@ -1473,6 +1489,89 @@
 
     </section>
 
+    <section id="limits-windows">
+
+      <title>Windows Platform Limitations</title>
+
+      <para>
+        The following limitations apply only to the Windows platform:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            The number of open file descriptors on Windows is limited to
+            a maximum of 2048, which may limit the ability to open a
+            large number of tables simultaneously. This limit is due to
+            the compatibility functions used to open files on Windows
+            that use the POSIX compatibility layer.
+          </para>
+
+          <para>
+            This limitation will also cause problems if you try to set
+            <option>max_open_files</option> to a value greater than the
+            2048 file limit.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            On Windows 32-bit platforms it is not possible to use more
+            than 2GB of RAM within a single process, including MySQL.
+            This is because the physical address limit on Windows 32-bit
+            is 4GB and the default setting within Windows is to split
+            the virtual address space between kernel (2GB) and
+            user/applications (2GB).
+          </para>
+
+          <para>
+            To use more memory than this you will need to use a 64-bit
+            version of Windows.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            When using <literal>MyISAM</literal> tables, you cannot use
+            aliases within Windows link to the data files on another
+            volume and then link back to the main MySQL
+            <option>datadir</option> location.
+          </para>
+
+          <para>
+            This facility is often used to move the data and index files
+            to a RAID or other fast solution, while retaining the main
+            <filename>.FRM</filename> files in the default data
+            directory configured with the <option>datadir</option>
+            option.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            The timers within MySQL used on Windows are of a lower
+            precision than the timers used on Linux. For most situations
+            you may not notice a difference, but the delay implied by a
+            call to <function role="sql">SLEEP()</function> on Windows
+            and Linux may differ slightly due to the differences in
+            precision.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            There is no 64-bit OLEDB Provider for ODBC (MSDASQL) in any
+            64-bit Windows operating system up to and including Windows
+            Vista. In practical terms this means that you can't use the
+            MySQL ODBC driver from ADO and other users of OLEDB.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+    </section>
+
   </section>
 
 </appendix>


Modified: trunk/it/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/it/refman-5.1/sql-syntax.xml	2008-03-07 19:46:28 UTC (rev 10164)
+++ trunk/it/refman-5.1/sql-syntax.xml	2008-03-07 20:45:22 UTC (rev 10165)
Changed blocks: 10, Lines Added: 70, Lines Deleted: 16; 5614 bytes

@@ -371,6 +371,10 @@
         commit.
       </para>
 
+      <para>
+        <literal>ALTER SERVER</literal> was added in MySQL 5.1.15.
+      </para>
+
     </section>
 
     <section id="alter-table">

@@ -2814,6 +2818,14 @@
         0.
       </para>
 
+      <note>
+        <para>
+          Note that the <literal>OWNER</literal> option is currently not
+          applied, and has no effect on the ownership or operation of
+          the server connection that is created.
+        </para>
+      </note>
+
       <para>
         The <literal>CREATE SERVER</literal> statement creates an entry
         in the <literal>mysql.server</literal> table that can later be

@@ -2858,6 +2870,10 @@
         commit.
       </para>
 
+      <para>
+        <literal>CREATE SERVER</literal> was added in MySQL 5.1.15.
+      </para>
+
     </section>
 
     <section id="create-table">

@@ -5664,6 +5680,10 @@
         commit.
       </para>
 
+      <para>
+        <literal>DROP SERVER</literal> was added in MySQL 5.1.15.
+      </para>
+
     </section>
 
     <section id="drop-table">

@@ -10489,6 +10509,14 @@
               syntax should be written literally; they are not
               metasyntax as used elsewhere in syntax descriptions.
             </para>
+
+            <para>
+              As of MySQL 5.1.24, you can use other types of joins
+              within <literal>{ OJ ... }</literal>, such as
+              <literal>INNER JOIN</literal> or <literal>RIGHT OUTER
+              JOIN</literal>. This helps with compatibility with some
+              third-party applications, but is not official ODBC syntax.
+            </para>
           </listitem>
 
           <listitem>

@@ -14552,12 +14580,12 @@
       </para>
 
       <para>
-        Beginning with MySQL 5.0.17, a new savepoint level is created
-        when a stored function is invoked or a trigger is activated. The
-        savepoints on previous levels become unavailable and thus do not
-        conflict with savepoints on the new level. When the function or
-        trigger terminates, any savepoints it created are released and
-        the previous savepoint level is restored.
+        A new savepoint level is created when a stored function is
+        invoked or a trigger is activated. The savepoints on previous
+        levels become unavailable and thus do not conflict with
+        savepoints on the new level. When the function or trigger
+        terminates, any savepoints it created are released and the
+        previous savepoint level is restored.
       </para>
 
     </section>

@@ -15863,6 +15891,15 @@
 
         <remark role="help-description-end"/>
 
+        <important>
+          <para>
+            This statement may be recorded in a history file such as
+            <filename>~/.mysql_history</filename>, which means that
+            plaintext passwords may be read by anyone having read access
+            to such files.
+          </para>
+        </important>
+
       </section>
 
       <section id="drop-user">

@@ -20890,7 +20927,8 @@
               </row>
               <row>
                 <entry><literal>connect_count</literal></entry>
-                <entry>The number of active connections to cluster data
nodes</entry>
+                <entry>The number of times this
<command>mysqld</command> has connected or
+                  reconnected to cluster data nodes</entry>
               </row>
             </tbody>
           </tgroup>

@@ -26655,21 +26693,37 @@
           an error.
         </para>
 
-        <para>
-          If you terminate a client session without deallocating a
-          previously prepared statement, the server deallocates it
-          automatically.
-        </para>
-
         <remark role="help-description-end"/>
       </listitem>
 
     </itemizedlist>
 
     <para>
+      A prepared statement is specific to the connection in which it was
+      created. If you terminate a client session without deallocating a
+      previously prepared statement, the server deallocates it
+      automatically.
+    </para>
+
+    <para>
+      A prepared statement is also global to the connection. If you
+      create a prepared statement within a stored routine, it is not
+      deallocated when the stored routine ends.
+    </para>
+
+    <para>
+      To guard against too many prepared statements being created
+      simultaneously, the <literal>max_prepared_stmt_count</literal>
+      system variable can be set.
+    </para>
+
+    <para>
       The following SQL statements can be used in prepared statements:
-      <literal>CREATE TABLE</literal>, <literal>DELETE</literal>,
-      <literal>DO</literal>, <literal>INSERT</literal>,
+      <literal>ALTER TABLE</literal> <literal>COMMIT</literal>
+      <literal>CREATE INDEX</literal> <literal>CREATE
TABLE</literal>,
+      <literal>DELETE</literal>, <literal>DO</literal>,
<literal>DROP
+      INDEX</literal> <literal>DROP TABLE</literal>
+      <literal>INSERT</literal>, <literal>RENAME TABLE</literal>
       <literal>REPLACE</literal>, <literal>SELECT</literal>,
       <literal>SET</literal>, <literal>UPDATE</literal>, and most
       <literal>SHOW</literal> statements.

@@ -26695,7 +26749,7 @@
 CACHE INDEX
 CHANGE MASTER
 CHECKSUM {TABLE | TABLES}
-{CREATE | RENAME | DROP} DATABASE
+{CREATE | DROP} DATABASE
 {CREATE | RENAME | DROP} USER
 FLUSH {TABLE | TABLES | TABLES WITH READ LOCK | HOSTS | PRIVILEGES
   | LOGS | STATUS | MASTER | SLAVE | DES_KEY_FILE | USER_RESOURCES}


Modified: trunk/pt/refman-5.1/dba-core.xml
===================================================================
--- trunk/pt/refman-5.1/dba-core.xml	2008-03-07 19:46:28 UTC (rev 10164)
+++ trunk/pt/refman-5.1/dba-core.xml	2008-03-07 20:45:22 UTC (rev 10165)
Changed blocks: 1, Lines Added: 24, Lines Deleted: 0; 1371 bytes

@@ -13031,6 +13031,30 @@
 
           <listitem>
             <para>
+              If a statement is logged by row and the client that
+              executed the statement has any temporary tables, then
+              logging by row is used for all subsequent statements
+              (except for those accessing temporary tables) until all
+              temporary tables in use by that client are dropped
+            </para>
+
+            <para>
+              This is true whether or not any temporary tables are
+              actually logged
+            </para>
+
+            <para>
+              Temporary tables cannot be logged using the row-based
+              format; thus, once row-based logging is used, all
+              subsequent statements using that table are unsafe, and we
+              approximate this condition by treating all statements made
+              by that client as unsafe until the client no longer holds
+              any temporary tables
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
               Beginning with MySQL 5.1.23:
 
               <itemizedlist>


Modified: trunk/pt/refman-5.1/restrictions.xml
===================================================================


Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 113 bytes