svn commit - mysqldoc@docsrva: r10009 - in trunk: dynamic-docs/changelog userguide workbench

[plavin]

Author: plavin
Date: 2008-02-25 21:31:03 +0100 (Mon, 25 Feb 2008)
New Revision: 10009

Log:

Document bugs:
32959, 33367, 34249, 34408, 34543, 34548, 34601, 34668, 32549, 32981,
32588, 33646, 34418 


Modified:
   trunk/dynamic-docs/changelog/workbench-versions.xml
   trunk/dynamic-docs/changelog/workbench.xml
   trunk/userguide/about.xml
   trunk/workbench/reference.xml
   trunk/workbench/tables.xml


Modified: trunk/dynamic-docs/changelog/workbench-versions.xml
===================================================================
--- trunk/dynamic-docs/changelog/workbench-versions.xml	2008-02-25 20:00:06 UTC (rev
10008)
+++ trunk/dynamic-docs/changelog/workbench-versions.xml	2008-02-25 20:31:03 UTC (rev
10009)
Changed blocks: 2, Lines Added: 13, Lines Deleted: 1; 862 bytes

@@ -4,7 +4,7 @@
 
   <mysqlproductname title="MySQL Workbench"/>
   
-    <versionentry ver="5.0.14beta" reldate="Not yet released">
+    <versionentry ver="5.0.14beta" reldate="25 February 2008">
       
     <versionentrypreamble>
 

@@ -14,6 +14,18 @@
 
     </versionentrypreamble>
     
+    </versionentry>
+  
+  <versionentry ver="5.0.15beta" reldate="Not yet released">
+    
+    <versionentrypreamble>
+      
+      <para>
+        <!--Not used but could add notes here-->
+      </para>
+      
+    </versionentrypreamble>
+    
   </versionentry>
   
 </versionlog>


Modified: trunk/dynamic-docs/changelog/workbench.xml
===================================================================
--- trunk/dynamic-docs/changelog/workbench.xml	2008-02-25 20:00:06 UTC (rev 10008)
+++ trunk/dynamic-docs/changelog/workbench.xml	2008-02-25 20:31:03 UTC (rev 10009)
Changed blocks: 1, Lines Added: 272, Lines Deleted: 0; 7885 bytes

@@ -5,6 +5,278 @@
 %all.entities;
 ]>
 <changelog>
+  
+  <!--logentry entrytype="bug">
+    <bugs>
+      <fixes bugid=""/>
+    </bugs>
+    <versions>
+      <version ver="5.0.14beta"/>
+    </versions>
+    <message>
+      <para>
+        
+      </para>
+    </message>
+    </logentry-->
+  
+  <logentry entrytype="bug">
+    <bugs>
+    <fixes bugid="34601"/>
+    </bugs>
+    <versions>
+    <version ver="5.0.14beta"/>
+    </versions>
+    <message>
+    <para>
+     After placing related tables on an EER diagram and then removing them using
+     the <guimenu>Undo</guimenu> menu option,
+      the connection lines between related tables no longer showed up.
+    </para>
+    </message>
+  </logentry>
+  
+  <logentry entrytype="bug">
+    <bugs>
+      <fixes bugid="34668"/>
+    </bugs>
+    <versions>
+      <version ver="5.0.14beta"/>
+    </versions>
+    <message>
+      <para>
+        When exporting an SQL CREATE script it was possible to
+        create two tables in the same schema with the same name.
+      </para>
+    </message>
+  </logentry>
+  
+  <logentry entrytype="bug">
+    <bugs>
+      <fixes bugid="32549"/>
+    </bugs>
+    <versions>
+      <version ver="5.0.14beta"/>
+    </versions>
+    <message>
+      <para>
+        It was not possible to drag or resize tables on an
+        EER diagram. Tables can now be manually resized.
+        To revert a table 
+        to automatic sizing use the <literal> Property </literal>
+        palette and set <literal>manualSizing</literal>to True.
+      </para>
+    </message>
+  </logentry>
+  
+  <logentry entrytype="bug">
+    <bugs>
+      <fixes bugid="32981"/>
+    </bugs>
+    <versions>
+      <version ver="5.0.14beta"/>
+    </versions>
+    <message>
+      <para>
+        It was not possible to
+        resize a table that used the <literal>Workbench (Default)</literal>
+        object notation. This was problematic for a number of reasons:
+        
+        <itemizedlist>
+          <listitem>
+            <para>
+              Long table names make the table very wide.
+            </para>
+          </listitem>
+          <listitem>
+            <para>
+              
+            </para>
+          </listitem>
+          <listitem>
+            <para>
+              Column definitions that are long relative to the table name,
+              are truncated.
+            </para>
+          </listitem>
+          <listitem>
+            <para>
+              Even if you trimmed column names using the
<guilabel>Diagram</guilabel>
+              tab of the <literal>Workbench Options</literal> the names were
+              sometimes truncated bled over the table border.
+            </para>
+          </listitem>
+        </itemizedlist>
+        
+       This has been corrected.
+      </para>
+    </message>
+  </logentry>
+  
+  <logentry entrytype="bug">
+    <bugs>
+      <fixes bugid="32588"/>
+    </bugs>
+    <versions>
+      <version ver="5.0.14beta"/>
+    </versions>
+    <message>
+      <para>
+        When there were two schemata and two EER diagrams    
+        tables did not show up on the EER diagram
+        if tables from different schemata 
+        were added to different EER diagrams.        
+        This was caused by defective software rendering.
+      </para>
+    </message>
+  </logentry>
+  
+  <logentry entrytype="bug">
+    <bugs>
+      <fixes bugid="33646"/>
+    </bugs>
+    <versions>
+      <version ver="5.0.14beta"/>
+    </versions>
+    <message>
+      <para>
+        When there were many tables on an EER
+        diagram, constant screen refreshing made the
+        application unusable. The performance of the software 
+        rendering mode has been improved.
+      </para>
+    </message>
+  </logentry>
+  
+  <logentry entrytype="bug">
+    <bugs>
+      <fixes bugid="34418"/>
+    </bugs>
+    <versions>
+      <version ver="5.0.14beta"/>
+    </versions>
+    <message>
+      <para>
+        Setting a column to <literal>AUTO_INCREMENT</literal>
+        caused the application to crash.
+      </para>
+    </message>
+  </logentry>
+  
+  <logentry entrytype="bug">
+    <bugs>
+      <fixes bugid="23959"/>
+    </bugs>
+    <versions>
+      <version ver="5.0.14beta"/>
+    </versions>
+    <message>
+      <para>
+        The display turned black when the application was resized.
+        This happened when viewing the <literal>MySQL Model</literal>
+        page or when viewing an EER diagram.
+      </para>
+    </message>
+  </logentry>
+  
+  <logentry entrytype="bug">
+    <bugs>
+      <fixes bugid="33367"/>
+    </bugs>
+    <versions>
+      <version ver="5.0.14beta"/>
+    </versions>
+    <message>
+      <para>
+        A table with many columns did not display
+        properly.  When the table was expanded on an EER
+        diagram it was impossible to scroll down and view all
+        the columns. Improved rendering has helped solve this problem.
+        However, for very large tables you may have to increase the
+        size of an EER. To do this use the <guimenu>Model</guimenu>,
+        <guimenu>Diagram Size ...</guimenu> menu option.
+      </para>
+    </message>
+  </logentry>
+  
+  <logentry entrytype="bug">
+    <bugs>
+      <fixes bugid="34249"/>
+    </bugs>
+    <versions>
+      <version ver="5.0.14beta"/>
+    </versions>
+    <message>
+      <para>
+        When a table's <literal>expanded</literal> property
+        was set to <literal>0</literal>, the connection line
+        between related tables, appeared at a diagonal
+        orientation. A connection line is
+        now docked on the sides of a table
+        even wghen the <literal>expanded</literal> property
+        is set to <literal>0</literal>.
+      </para>
+    </message>
+  </logentry>
+  
+  <logentry entrytype="bug">
+    <bugs>
+      <fixes bugid="34408"/>
+    </bugs>
+    <versions>
+      <version ver="5.0.14beta"/>
+    </versions>
+    <message>
+      <para>
+        It was reported that you could not add a primary key
+        to a table imported from a MySQL <literal>CREATE</literal>
+        script.  This was not true but did highlight the
+        fact that the method for adding a primary key was not obvious.
+        Now, in addition to adding a primary key by double clicking
+        the icon to the left of a column in the table editor view,
+        you can also add a primary key by checking the 
+        <literal>PRIMARY KEY</literal> checkbox in the 
+        <literal>Column Details</literal> section of the table editor.
+      </para>
+    </message>
+  </logentry>
+  
+  <logentry entrytype="bug">
+    <bugs>
+      <fixes bugid="34543"/>
+    </bugs>
+    <versions>
+      <version ver="5.0.14beta"/>
+    </versions>
+    <message>
+      <para>
+        If there was a relationship between table <literal>A</literal>
+        and table <literal>B</literal> and also one between table
<literal>B</literal>
+        and table <literal>A</literal>, the connection lines appeared on top
of
+        each other. Connection lines now appear attached at the 
+        related columns.
+      </para>
+    </message>
+  </logentry>
+  
+  <logentry entrytype="bug">
+    <bugs>
+      <fixes bugid="34548"/>
+    </bugs>
+    <versions>
+      <version ver="5.0.14beta"/>
+    </versions>
+    <message>
+      <para>
+        When choosing the <guimenu>Export as PNG</guimenu> menu 
+        option the file dialogue box file type was <literal>All
+        Files</literal>instead of <literal>PNG</literal>. 
+        The same was true for <guimenu>Export as singlePage PDF</guimenu>
+        and <guimenu>Export as singlePage PS</guimenu>.        
+        The default is now the appropriate file type.          
+      </para>
+    </message>
+  </logentry>
 
   <logentry entrytype="bug">
     <bugs>


Modified: trunk/userguide/about.xml
===================================================================
--- trunk/userguide/about.xml	2008-02-25 20:00:06 UTC (rev 10008)
+++ trunk/userguide/about.xml	2008-02-25 20:31:03 UTC (rev 10009)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 12; 1027 bytes

@@ -127,18 +127,6 @@
       piece of MySQL documentation &mdash; The &userguide;.
     </para>
 
-    <para>
-      If your submission is accepted you will receive credit for your
-      contribution or you may remain anonymous if you prefer. For an
-      example attribution see
-      <ulink url="http://dev.mysql.com/doc/query-browser/it/index.html
attribution">
-      attribution</ulink>. An attribution would normally include your
-      name, a short biography, your email address, and perhaps a link to
-      your website. Since the &userguide; is published under the GFDL,
-      you may of course publish it elsewhere in any way you choose, in
-      accordance with the GFDL of course.
-    </para>
-
     <section id="userguide-contribution-checklist">
 
       <title>Contribution Checklist</title>


Modified: trunk/workbench/reference.xml
===================================================================
--- trunk/workbench/reference.xml	2008-02-25 20:00:06 UTC (rev 10008)
+++ trunk/workbench/reference.xml	2008-02-25 20:31:03 UTC (rev 10009)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 0; 662 bytes

@@ -774,6 +774,12 @@
               dialog box to adjust the width or height of the canvas.
               The unit of measure is pages; the default value is two.
             </para>
+            
+            <para>
+              When you have tables with numerous
+              columns,  use this menu option to  increase the
+              size of the EER.
+            </para>
           </listitem>
 
           <listitem>


Modified: trunk/workbench/tables.xml
===================================================================
--- trunk/workbench/tables.xml	2008-02-25 20:00:06 UTC (rev 10008)
+++ trunk/workbench/tables.xml	2008-02-25 20:31:03 UTC (rev 10009)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 1; 760 bytes

@@ -476,7 +476,9 @@
         the column is a member of the primary key. If the icon is a
         small key, that column belongs to the primary key, otherwise the
         icon is a blue diamond. To add or remove a column from the
-        primary key, double click on the icon.
+        primary key, double click on the icon. You can also add a primary
+        key by checking the <literal>PRIMARY KEY</literal> checkbox in the 
+        <literal>Column Details</literal> section of the table editor.
       </para>
 
     </section>