svn commit - mysqldoc@docsrva: r5525 - trunk/userguide

[plavin]

Author: plavin
Date: 2007-03-23 16:17:40 +0100 (Fri, 23 Mar 2007)
New Revision: 5525

Log:
Clean up section

Modified:
   trunk/userguide/excel-mysql.xml


Modified: trunk/userguide/excel-mysql.xml
===================================================================
--- trunk/userguide/excel-mysql.xml	2007-03-23 14:50:11 UTC (rev 5524)
+++ trunk/userguide/excel-mysql.xml	2007-03-23 15:17:40 UTC (rev 5525)
Changed blocks: 3, Lines Added: 46, Lines Deleted: 27; 4742 bytes

@@ -803,19 +803,19 @@
     <title>Confirming Data Integrity</title>
 
     <para>
-      It's always wise to check the state of your transformed data. There's no
-      substitute for visual inspection but there are a variety of ways
-      to check your data using SQL.
+      It's always wise to check the state of your transformed data.
+      There's no substitute for visual inspection but there are a
+      variety of ways to check your data using SQL.
     </para>
 
     <para>
-      For example, there should be no orphaned member parecords. Since we've
-      migrated from a flat-table database that contained all the
+      For example, there should be no orphaned member records. Since
+      we've migrated from a flat-table database that contained all the
       original data, finding an id in the members table with no
-      corresponding record in the member accreditations table would indicate
-      that something was wrong.
-      The following SQL statement will return all records in the members
-      table that don't have matching records in the member accreditations table:
+      corresponding record in the member accreditations table would
+      indicate that something was wrong. The following SQL statement
+      will return all records in the members table that don't have
+      matching records in the member accreditations table:
     </para>
 
 <programlisting>

@@ -834,14 +834,16 @@
     <para>
       An easy way to reuse this SQL statement is to save it as a view.
       To do this using Query Browser, make sure the
-      <literal>spreadsheet</literal> database is active, then right click
-      on any one of the tables in the <literal>Schemata</literal> window
-      and choose the <guimenu>Create View</guimenu> option. Clicking
-      <guibutton>Okay</guibutton> after entering a viepaw name opens a new
-      tab displaying the basic syntax for creating a view. Paste the
-      preceding SQL statement into the <literal>AS</literal> clause and
-      execute the query. After refreshing the schemata the new view
-      should show up.
+      <literal>spreadsheet</literal> database is active, then right
+      click on any one of the tables in the <literal>Schemata</literal>
+      window and choose the <guimenu>Create View</guimenu> option.
+      Clicking <guibutton>Okay</guibutton> after entering a view name
+      opens a new tab displaying the basic syntax for creating a view.
+      Paste the preceding SQL statement into the <literal>AS</literal>
+      clause and execute the query. After refreshing the schemata the
+      new view should show up. You can view the record set associated
+      with this view in exactly the same way that you would view the
+      record set associated with a table.
     </para>
 
     <para>

@@ -859,23 +861,40 @@
     </programlisting>
 
     <para>
-      Again, convert this to a view using the procedure described above.
+      Again, to preserve this SQL statement, convert it to a view using
+      the procedure described above.
     </para>
 
     <para>
-      check for duplicate certification numbers 
-      
-      SELECT
-      count(t.`certificationnumber`), t.`certificationnumber` FROM
-      tblmemberaccreditations t Group by (t.`certificationnumber`)
-      Having count(t.`certificationnumber`) > 1; You can also make
-      changes to the data from within Query Browser.
+      There are also various other ways of querying your records to
+      verify the data. For example, if all certification numbers in the
+      member accreditations table are meant to be unique, 
+      executing the following query confirms this:
     </para>
-    
+
+<programlisting>
+SELECT COUNT(t.`certificationnumber`), t.`certificationnumber` 
+  FROM tblmemberaccreditations t 
+  GROUP BY (t.`certificationnumber`)
+  HAVING COUNT.`certificationnumber`) > 1;     
+    </programlisting>
+
     <para>
-      edit records from within Query Browser
+      If you notice discrepancies in the data and wish to update records
+      you can also do this from within Query Browser. Click the
+      <guibutton>Start Editing</guibutton> button and then select the
+      record you wish to change and place the cursor in the
+      column you wish to change.
     </para>
 
+    <note>
+      <para>
+        Only record sets created from a single table that has a primary
+        key are editable. If the <guibutton>Start Editing</guibutton>
+        button is disabled the record set is not editable.
+      </para>
+    </note>
+
   </section>
 
   <section id="production-database">