svn commit - mysqldoc@docsrva: r12406 - trunk/dynamic-docs/changelog

[anthony.bedford]

Author: tbedford
Date: 2008-11-11 12:34:25 +0100 (Tue, 11 Nov 2008)
New Revision: 12406

Log:
Added entries for bugs #37178, #39983, #40426, #39257, #39989, #39476.

Modified:
   trunk/dynamic-docs/changelog/workbench.xml


Modified: trunk/dynamic-docs/changelog/workbench.xml
===================================================================
--- trunk/dynamic-docs/changelog/workbench.xml	2008-11-11 06:33:45 UTC (rev 12405)
+++ trunk/dynamic-docs/changelog/workbench.xml	2008-11-11 11:34:25 UTC (rev 12406)
Changed blocks: 1, Lines Added: 141, Lines Deleted: 0; 3062 bytes

@@ -9,6 +9,147 @@
   <logentry entrytype="bug">
 
     <bugs>
+      <fixes bugid="39476"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.0.27"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The <guimenu>Copy SQL to Clipboard</guimenu> action (right click
+        menu on table) did not use Windows-compatible line endings.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="39989"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.0.27"/>
+    </versions>
+
+    <message>
+
+      <para>
+        If a trigger was renamed, and the design then synched with a
+        database instance, the generated SQL created a trigger with the
+        new name and then dropped the trigger with the old name. This
+        resulted in the following error:
+      </para>
+
+<programlisting>
+Error 1235: This version of MySQL doesn't yet support 
+&apos;multiple triggers with the same action time and event for one table&apos;
+</programlisting>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="39257"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.0.27"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When a column had a datatype <literal>BOOLEAN</literal> and it
+        was exported using <guimenu>Forward Engineer SQL
+        ALTER</guimenu>, the exported type was
+        <literal>BOOLEAN(2)</literal> instead of
+        <literal>BOOLEAN</literal>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="40426"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.0.27"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When a stored routine was edited, the edit cursor jumped back to
+        the start of the page unless typing was constant.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="39983"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.4"/>
+    </versions>
+
+    <message>
+
+      <para>
+        A model created using the Windows version of Workbench caused
+        the Linux version of Workbench to crash on loading the model.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="37178"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.0.27"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When a DBDesigner model with 333 tables was imported into
+        Workbench the RAM usage went up to approximately 1GB. Workbench
+        then crashed with the following exception:
+      </para>
+
+<programlisting>
+  Error creating cairo context: out of memory
+</programlisting>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
       <fixes bugid="38439"/>
     </bugs>