svn commit - mysqldoc@oter02: r26258 - trunk/dynamic-docs/glossary

[john.russell]

Author: jdrussel
Date: 2011-05-18 01:49:43 +0200 (Wed, 18 May 2011)
New Revision: 26258

Log:
More Q&A for readers who reach the glossary from Ref Man links and might not know backup terminology.


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


Modified: trunk/dynamic-docs/glossary/backup.xml
===================================================================
--- trunk/dynamic-docs/glossary/backup.xml	2011-05-17 23:40:38 UTC (rev 26257)
+++ trunk/dynamic-docs/glossary/backup.xml	2011-05-17 23:49:43 UTC (rev 26258)
Changed blocks: 2, Lines Added: 16, Lines Deleted: 2; 1503 bytes

@@ -698,6 +698,8 @@
     <gterm>MySQL Enterprise Backup</gterm>
     <def>
 
+<!-- JDR: if this is a common landing point for links from other docs, beef up the definition
+		 for first-time users who aren't familiar with these concepts. -->
       <para>
         A licensed product, superceding InnoDB Hot Backup, that performs
         <emphasis role="bold">hot backups</emphasis> of MySQL databases.

@@ -717,10 +719,22 @@
     <gterm>MyISAM</gterm>
     <def>
 
-      <para></para>
+      <para>
+        A MySQL storage engine, formerly the default for new tables. In
+        MySQL 5.5 and higher, <emphasis role="bold">InnoDB</emphasis>
+        becomes the default storage engine. MySQL Enterprise Backup can
+        back up both types of tables, and tables from other storage
+        engines also. The backup process for InnoDB tables
+        (<emphasis role="bold">hot backup</emphasis>) is less disruptive
+        to database operations than for MyISAM tables
+        (<emphasis role="bold">warm backup</emphasis>).
+      </para>
 
     </def>
-    <gseealso glosid=""/>
+    <gseealso glosid="mysql_enterprise_backup"/>
+    <gseealso glosid="innodb"/>
+    <gseealso glosid="hot_backup"/>
+    <gseealso glosid="warm_backup"/>
 
   </glossent>