List:Commits« Previous MessageNext Message »
From:paul.dubois Date:October 18 2010 2:07pm
Subject:svn commit - mysqldoc@docsrva: r23184 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0
View as plain text  
Author: paul
Date: 2010-10-18 16:07:40 +0200 (Mon, 18 Oct 2010)
New Revision: 23184

Log:
 r64291@frost:  paul | 2010-10-18 08:30:56 -0500
 Clarification about internal temporary tables


Modified:
   trunk/refman-4.1/optimization.xml
   trunk/refman-5.0/optimization.xml
   trunk/refman-5.1/optimization.xml
   trunk/refman-5.5/optimization.xml
   trunk/refman-5.6/optimization.xml
   trunk/refman-6.0/optimization.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:43274
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:64271
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:43274
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:64291
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-4.1/optimization.xml
===================================================================
--- trunk/refman-4.1/optimization.xml	2010-10-18 13:51:57 UTC (rev 23183)
+++ trunk/refman-4.1/optimization.xml	2010-10-18 14:07:40 UTC (rev 23184)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 3; 1008 bytes

@@ -8985,9 +8985,11 @@
         while processing queries. Such a table can be held in memory and
         processed by the <literal>MEMORY</literal> storage engine, or
         stored on disk and processed by the <literal>MyISAM</literal>
-        storage engine. A temporary table created initially as an
-        in-memory table may be converted to an on-disk table if it
-        becomes too large.
+        storage engine. The server may create a temporary table
+        initially as an in-memory table,then convert it to an on-disk
+        table if it becomes too large. Users have no direct control over
+        when the server creates an internal temporary table or which
+        storage engine the server uses to manage it.
       </para>
 
       <para>


Modified: trunk/refman-5.0/optimization.xml
===================================================================
--- trunk/refman-5.0/optimization.xml	2010-10-18 13:51:57 UTC (rev 23183)
+++ trunk/refman-5.0/optimization.xml	2010-10-18 14:07:40 UTC (rev 23184)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 3; 1010 bytes

@@ -11424,9 +11424,11 @@
         while processing queries. Such a table can be held in memory and
         processed by the <literal>MEMORY</literal> storage engine, or
         stored on disk and processed by the <literal>MyISAM</literal>
-        storage engine. A temporary table created initially as an
-        in-memory table may be converted to an on-disk table if it
-        becomes too large.
+        storage engine. The server may create a temporary table
+        initially as an in-memory table,then convert it to an on-disk
+        table if it becomes too large. Users have no direct control over
+        when the server creates an internal temporary table or which
+        storage engine the server uses to manage it.
       </para>
 
       <para>


Modified: trunk/refman-5.1/optimization.xml
===================================================================
--- trunk/refman-5.1/optimization.xml	2010-10-18 13:51:57 UTC (rev 23183)
+++ trunk/refman-5.1/optimization.xml	2010-10-18 14:07:40 UTC (rev 23184)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 3; 1010 bytes

@@ -12719,9 +12719,11 @@
         while processing queries. Such a table can be held in memory and
         processed by the <literal>MEMORY</literal> storage engine, or
         stored on disk and processed by the <literal>MyISAM</literal>
-        storage engine. A temporary table created initially as an
-        in-memory table may be converted to an on-disk table if it
-        becomes too large.
+        storage engine. The server may create a temporary table
+        initially as an in-memory table,then convert it to an on-disk
+        table if it becomes too large. Users have no direct control over
+        when the server creates an internal temporary table or which
+        storage engine the server uses to manage it.
       </para>
 
       <para>


Modified: trunk/refman-5.5/optimization.xml
===================================================================
--- trunk/refman-5.5/optimization.xml	2010-10-18 13:51:57 UTC (rev 23183)
+++ trunk/refman-5.5/optimization.xml	2010-10-18 14:07:40 UTC (rev 23184)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 3; 1070 bytes

@@ -3587,9 +3587,12 @@
           while processing queries. Such a table can be held in memory
           and processed by the <literal>MEMORY</literal> storage engine,
           or stored on disk and processed by the
-          <literal>MyISAM</literal> storage engine. A temporary table
-          created initially as an in-memory table may be converted to an
-          on-disk table if it becomes too large.
+          <literal>MyISAM</literal> storage engine. The server may
+          create a temporary table initially as an in-memory table,then
+          convert it to an on-disk table if it becomes too large. Users
+          have no direct control over when the server creates an
+          internal temporary table or which storage engine the server
+          uses to manage it.
         </para>
 
         <para>


Modified: trunk/refman-5.6/optimization.xml
===================================================================
--- trunk/refman-5.6/optimization.xml	2010-10-18 13:51:57 UTC (rev 23183)
+++ trunk/refman-5.6/optimization.xml	2010-10-18 14:07:40 UTC (rev 23184)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 3; 1010 bytes

@@ -13180,9 +13180,11 @@
         while processing queries. Such a table can be held in memory and
         processed by the <literal>MEMORY</literal> storage engine, or
         stored on disk and processed by the <literal>MyISAM</literal>
-        storage engine. A temporary table created initially as an
-        in-memory table may be converted to an on-disk table if it
-        becomes too large.
+        storage engine. The server may create a temporary table
+        initially as an in-memory table,then convert it to an on-disk
+        table if it becomes too large. Users have no direct control over
+        when the server creates an internal temporary table or which
+        storage engine the server uses to manage it.
       </para>
 
       <para>


Modified: trunk/refman-6.0/optimization.xml
===================================================================
--- trunk/refman-6.0/optimization.xml	2010-10-18 13:51:57 UTC (rev 23183)
+++ trunk/refman-6.0/optimization.xml	2010-10-18 14:07:40 UTC (rev 23184)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 3; 1010 bytes

@@ -13810,9 +13810,11 @@
         while processing queries. Such a table can be held in memory and
         processed by the <literal>MEMORY</literal> storage engine, or
         stored on disk and processed by the <literal>MyISAM</literal>
-        storage engine. A temporary table created initially as an
-        in-memory table may be converted to an on-disk table if it
-        becomes too large.
+        storage engine. The server may create a temporary table
+        initially as an in-memory table,then convert it to an on-disk
+        table if it becomes too large. Users have no direct control over
+        when the server creates an internal temporary table or which
+        storage engine the server uses to manage it.
       </para>
 
       <para>


Thread
svn commit - mysqldoc@docsrva: r23184 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0paul.dubois18 Oct