List:Commits« Previous MessageNext Message »
From:john.russell Date:July 29 2010 10:29pm
Subject:svn commit - mysqldoc@docsrva: r21988 - trunk/refman-5.5
View as plain text  
Author: jrussell
Date: 2010-07-30 00:29:18 +0200 (Fri, 30 Jul 2010)
New Revision: 21988

Log:
Added some intro text for INSERT / UPDATE / DELETE section.
A couple of other editorial edits.
Fixed a couple of typos.


Modified:
   trunk/refman-5.5/optimization.xml


Modified: trunk/refman-5.5/optimization.xml
===================================================================
--- trunk/refman-5.5/optimization.xml	2010-07-29 19:35:26 UTC (rev 21987)
+++ trunk/refman-5.5/optimization.xml	2010-07-29 22:29:18 UTC (rev 21988)
Changed blocks: 3, Lines Added: 22, Lines Deleted: 4; 2461 bytes

@@ -6701,8 +6701,8 @@
               for obtaining the types of the result columns. (This trick
               does not work in the MySQL Monitor (the
               <command>mysql</command> program), which merely displays
-              <literal>Empty set</literal> in such cases; you should
-              instead use <literal role="stmt">SHOW COLUMNS</literal> or
+              <literal>Empty set</literal> in such cases; instead, use
+              <literal role="stmt">SHOW COLUMNS</literal> or
               <literal role="stmt">DESCRIBE</literal> for this purpose.)
             </para>
           </listitem>

@@ -6842,8 +6842,27 @@
 
     <section id="non-select-optimization">
 
-      <title>Optimizing Non-<literal role="stmt">SELECT</literal> Statements</title>
+      <title>Optimizing DML Statements</title>
 
+      <para>
+        This section explains how to speed up the data manipulation
+        language (DML) statements,
+        <literal role="stmt">INSERT</literal>,
+        <literal role="stmt">UPDATE</literal>, and
+        <literal role="stmt">DELETE</literal>. Traditional OLTP
+        applications and modern web applications typically do many small
+        DML operations, where concurrency is vital. Data analysis and
+        reporting applications typically run DML operations that affect
+        many rows at once, where the main considerations is the I/O to
+        write large amounts of data and keep indexes up-to-date. For
+        inserting and updating large volumes of data (known in the
+        industry as ETL, for <quote>extract-transform-load</quote>),
+        sometimes you use other SQL statements or external commands,
+        that mimic the effects of <literal role="stmt">INSERT</literal>,
+        <literal role="stmt">UPDATE</literal>, and
+        <literal role="stmt">DELETE</literal> statements.
+      </para>
+
       <section id="insert-speed">
 
         <title>Speed of <literal role="stmt">INSERT</literal> Statements</title>

@@ -8455,7 +8474,6 @@
           <para>
             Use <literal>AUTO_INCREMENT</literal> columns so that each
             row in a table can be identified by a single unique value.
-            unique values.
           </para>
         </listitem>
 


Thread
svn commit - mysqldoc@docsrva: r21988 - trunk/refman-5.5john.russell30 Jul