List:Commits« Previous MessageNext Message »
From:john.russell Date:March 21 2011 7:19pm
Subject:svn commit - mysqldoc@oter02: r25464 - trunk/dynamic-docs/glossary
View as plain text  
Author: jdrussel
Date: 2011-03-21 20:19:17 +0100 (Mon, 21 Mar 2011)
New Revision: 25464

Log:
InnoDB terminology tends towards the low-level and internal.
Adding definitions for SQL-level terms such as row and column.


Modified:
   trunk/dynamic-docs/glossary/innodb.xml


Modified: trunk/dynamic-docs/glossary/innodb.xml
===================================================================
--- trunk/dynamic-docs/glossary/innodb.xml	2011-03-21 18:52:18 UTC (rev 25463)
+++ trunk/dynamic-docs/glossary/innodb.xml	2011-03-21 19:19:17 UTC (rev 25464)
Changed blocks: 5, Lines Added: 83, Lines Deleted: 13; 5429 bytes

@@ -894,6 +894,34 @@
 
   </glossent>
 
+  <glossent id="column">
+
+    <gterm>column</gterm>
+    <def>
+
+      <para>
+        A data item within a <emphasis role="bold">row</emphasis>, whose
+        storage and semantics are defined by a data type. Each
+        <emphasis role="bold">table</emphasis> and
+        <emphasis role="bold">index</emphasis> is largely defined by the
+        set of columns it contains.
+      </para>
+      <para>
+        In discussions of MySQL internal operations, sometimes
+        <emphasis role="bold">field</emphasis> is used as a synonym,
+        while row is the preferred term when discussing
+        <emphasis role="bold">SQL</emphasis>.
+      </para>
+
+    </def>
+    <gseealso glosid="row"/>
+    <gseealso glosid="table"/>
+    <gseealso glosid="index"/>
+    <gseealso glosid="field"/>
+    <gseealso glosid="sql"/>
+
+  </glossent>
+
   <glossent id="column_index">
 
     <gterm>column index</gterm>

@@ -4512,22 +4540,30 @@
         A unit representing how much data InnoDB transfers at any one
         time between disk (the <emphasis role="bold">data
         files</emphasis>) and memory (the <emphasis role="bold">buffer
-        pool</emphasis>). A page can contain one or more rows, depending
-        on how much data is in each row. If a row does not fit entirely
-        into a single page, InnoDB sets up additional pointer-style data
+        pool</emphasis>). A page can contain one or more
+        <emphasis role="bold">rows</emphasis>, depending on how much
+        data is in each row. If a row does not fit entirely into a
+        single page, InnoDB sets up additional pointer-style data
         structures so that the information about the row can be stored
         in one page.
       </para>
       <para>
         One way to fit more data in each page is to use
-        <emphasis role="bold">compressed row format</emphasis>.
+        <emphasis role="bold">compressed row format</emphasis>. For
+        tables that use BLOBs or large text fields,
+        <emphasis role="bold">compact row format</emphasis> allows those
+        large columns to be stored separately from the rest of the row,
+        reducing I/O overhead and memory usage for queries that do not
+        reference those columns.
       </para>
 
     </def>
     <gseealso glosid="data_files"/>
     <gseealso glosid="buffer_pool"/>
+    <gseealso glosid="row"/>
     <gseealso glosid="page_size"/>
     <gseealso glosid="compressed_row_format"/>
+    <gseealso glosid="compact_row_format"/>
 
   </glossent>
 

@@ -4537,11 +4573,12 @@
     <def>
 
       <para>
-        Currently, this value is fixed at 16 kilobytes. This is
-        considered a reasonable compromise: large enough to hold the
-        data for most rows, yet small enough to minimize the performance
-        overhead of transferring unneeded data to memory. Other values
-        are not tested or supported.
+        Currently, the size of each InnoDB
+        <emphasis role="bold">page</emphasis> is fixed at 16 kilobytes.
+        This is considered a reasonable compromise: large enough to hold
+        the data for most rows, yet small enough to minimize the
+        performance overhead of transferring unneeded data to memory.
+        Other values are not tested or supported.
       </para>
 
     </def>

@@ -4914,16 +4951,47 @@
 
   </glossent>
 
+  <glossent id="row">
+
+    <gterm>row</gterm>
+    <def>
+
+      <para>
+        The logical data structure defined by a set of
+        <emphasis role="bold">columns</emphasis>. A set of rows makes up
+        a <emphasis role="bold">table</emphasis>. Within InnoDB
+        <emphasis role="bold">data files</emphasis>, each
+        <emphasis role="bold">page</emphasis> can contain one or more
+        rows.
+      </para>
+      <para>
+        Although InnoDB uses the term <emphasis role="bold">row
+        format</emphasis> for consistency with MySQL syntax, the row
+        format is a property of each table and applies to all rows in
+        that table.
+      </para>
+
+    </def>
+    <gseealso glosid="column"/>
+    <gseealso glosid="table"/>
+    <gseealso glosid="data_files"/>
+    <gseealso glosid="page"/>
+    <gseealso glosid="row_format"/>
+
+  </glossent>
+
   <glossent id="row_format">
 
     <gterm>row format</gterm>
     <def>
 
       <para>
-        The disk storage format for a row from an InnoDB table. As
-        InnoDB gains new capabilities such as compression, new row
-        formats are introduced to support the resulting improvements in
-        storage efficiency and performance.
+        The disk storage format for a
+        <emphasis role="bold">row</emphasis> from an InnoDB
+        <emphasis role="bold">table</emphasis>. As InnoDB gains new
+        capabilities such as compression, new row formats are introduced
+        to support the resulting improvements in storage efficiency and
+        performance.
       </para>
       <para>
         Each table has its own row format, specified through the

@@ -4937,6 +5005,8 @@
       </para>
 
     </def>
+    <gseealso glosid="row"/>
+    <gseealso glosid="table"/>
     <gseealso glosid="fixed_row_format"/>
     <gseealso glosid="dynamic_row_format"/>
     <gseealso glosid="compact_row_format"/>


Thread
svn commit - mysqldoc@oter02: r25464 - trunk/dynamic-docs/glossaryjohn.russell21 Mar