Author: mcbrown
Date: 2008-03-15 13:32:38 +0100 (Sat, 15 Mar 2008)
New Revision: 10258
Log:
Documenting Workbench Bug fixes:
Bug #35227
Bug #34922
Bug #34822
Bug #35213
Bug #33980
Bug #34345
Bug #33477
Bug #32835
Bug #35186
Bug #35093
Bug #34975
Bug #35205
Bug #34784
Bug #34976
Bug #34500
Bug #35197
Bug #35237
Bug #34810
Bug #32320
Bug #34849
Bug #34857
Bug #34897
Bug #35127
Bug #35243
Bug #33265
Bug #32891
Some fixes to the Workbench installation/uninstall notes:
- Simplifying the structure for installation
- Extending some of the descriptions and warnings
- Merging Install/Uninstall content into the same chapter
Added:
trunk/workbench/renamed-nodes.txt
Removed:
trunk/workbench/uninstalling.xml
Modified:
trunk/dynamic-docs/changelog/workbench.xml
trunk/refman-common/connector-odbc.xml
trunk/workbench/Makefile.depends
trunk/workbench/editions.xml
trunk/workbench/installing.xml
trunk/workbench/workbench.xml
Modified: trunk/dynamic-docs/changelog/workbench.xml
===================================================================
--- trunk/dynamic-docs/changelog/workbench.xml 2008-03-15 12:16:43 UTC (rev 10257)
+++ trunk/dynamic-docs/changelog/workbench.xml 2008-03-15 12:32:38 UTC (rev 10258)
Changed blocks: 4, Lines Added: 824, Lines Deleted: 174; 28063 bytes
@@ -7,384 +7,1028 @@
<changelog>
<logentry entrytype="bug">
+
<bugs>
+ <fixes bugid="34922"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Editing a primary key column within a model on Microsoft Vista
+ could cause a crash.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="34822"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When editing a model, the windows and toolbars would realign
+ themselves during selection. This was related to the configured
+ font sizer the DPI setting of the monitor, causing the
+ application to redraw the windows to account for the
+ configuration combination.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="35213"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Generating an <literal>ALTER SCRIPT</literal> or using the
+ synchronize functionality on a model with entity relationships,
+ the relationship lines within the diagram would be generated
+ twice.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="33980"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When editing comments, the <keycap>Return</keycap> key would
+ move to the next column, which prevented the use of newlines
+ within the comment information. Workbench now allows use of the
+ <keycap>Return</keycap> key within the comment field.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="34345"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Deleting an existing schema with an open table editor would not
+ close the table editor window. The window is now closed when the
+ schema is deleted.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="33477"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Editing an existing diagram could cause an unhandled exception
+ on Windows Vista.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="32835"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When scrolling through a schema, the tables in the schema were
+ not redrawn correctly.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="35186"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Deleting objects within the overview pane when the corresponding
+ editor pane for those objects is open would cause a crash.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="35093"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When changing the name within a foreign key relationship, the
+ modified name is not reflected in the tables to which the
+ foreign key is related.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="34975"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When saving an existing model, the <guilabel>MySQL
+ Model</guilabel> overview panel would scroll to the top of the
+ model definition.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="35205"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Boolean values were unsupported when trying to insert values
+ into a table, the <literal>TRUE</literal> would instead be
+ replaced by a textual, quoted version <literal>'TRUE'</literal>.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="34784"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ The <guilabel>New File</guilabel> dialog box is non-modal, and
+ could be hidden by other windows. The dial box is now always
+ drawn on top of other windows.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="34976"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Creating a new file after changing an existing file with
+ modifications could lead to the original being deleted without
+ prompting to save the changes.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="34500"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Changing the column name of a table when you have pending
+ inserts to the table did not change the column name in the
+ corresponding <literal>INSERT</literal> statements.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="35197"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Printing a model diagram to PDF or Postscript, results in a
+ corrupt file PDF or Postscript file that does not match the
+ model.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="35237"/>
+ <fixes bugid="34810"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ A foreign key relationship to the source table (a reflexive
+ relationship) gives a bad representation in the entity model
+ diagram.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="32320"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Printing a model when there is no printer connected could result
+ in an application exception.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="34849"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Opening an existing MySQL Workbench file after associating the
+ <filename>.mwb</filename> extension with the application leads
+ to a crash when you open a MySQL Workbench file.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="34857"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ A new <guilabel>GRT Inspector</guilabel> tab would be created
+ every time the <guilabel>GRT Shell</guilabel> was opened. In
+ addition, manually closing the <guilabel>GRT
+ Inspector</guilabel> and <guilabel>GRT Shell</guilabel>
+ components would cause an exception.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="34897"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Incorrect <literal>ALTER</literal> statements are created during
+ the synchronization process if you add foreign keys to an
+ existing or imported model.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="35127"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When entering data into the <guilabel>Default</guilabel> column
+ of the table editor, the use of the <keycap>Return</keycap> key
+ for saving the information about the default value was not
+ supported.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="35243"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Using <guilabel>Undo</guilabel> on a relationship within a model
+ would cause an exception.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="33265"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Identifiers (tables, column, index, triggers and other data
+ types) could be created with names longer than the maximum
+ support by MySQL Server.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="32891"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.15beta"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Placing an object on the canvas of an EER diagram where you have
+ reverse engineered an existing database, would lead to multiple
+ copies of the object appearing on the diagram.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
<fixes bugid="35119"/>
</bugs>
+
<versions>
<version ver="5.0.15beta"/>
</versions>
+
<message>
+
<para>
- There was a typographical error in the help message
- for the GRT command <literal>cd</literal>. The word
- <literal>Absolute</literal> was missing the final <literal>e</literal>.
- This has been corrected.
+ There was a typographical error in the help message for the GRT
+ command <literal>cd</literal>. The word
+ <literal>Absolute</literal> was missing the final
+ <literal>e</literal>. This has been corrected.
</para>
+
</message>
- </logentry>
-
+
+ </logentry>
+
<logentry entrytype="bug">
+
<bugs>
- <fixes bugid="34170"/>
+ <fixes bugid="34170"/>
</bugs>
+
<versions>
- <version ver="5.0.15beta"/>
+ <version ver="5.0.15beta"/>
</versions>
+
<message>
- <para>
- Searching a project specifying <literal>Entire Model</literal>
- in the <literal>In Location:</literal> drop down list box
- did not return any results. This applied to
- the Standard Edition only.
- </para>
+
+ <para>
+ Searching a project specifying <literal>Entire Model</literal>
+ in the <literal>In Location:</literal> drop down list box did
+ not return any results. This applied to the Standard Edition
+ only.
+ </para>
+
</message>
+
</logentry>
-
+
<logentry entrytype="bug">
+
<bugs>
<fixes bugid="34148"/>
</bugs>
+
<versions>
<version ver="5.0.15beta"/>
</versions>
+
<message>
+
<para>
- When the page size was changed from A4 to
- B4 it was not possible to move objects
- on an EER diagram beyond the old page boundaries.
+ When the page size was changed from A4 to B4 it was not possible
+ to move objects on an EER diagram beyond the old page
+ boundaries.
</para>
+
</message>
+
</logentry>
-
+
<logentry entrytype="bug">
+
<bugs>
<fixes bugid="33818"/>
</bugs>
+
<versions>
<version ver="5.0.15beta"/>
</versions>
+
<message>
+
<para>
- Where relationship lines crossed, and
- one of the connectors was changed to <literal>Hidden</literal> or
- <literal>Draw Split</literal>, the semi circle that indicated
- the previous intersection was still shown on the remaining
- connector.
+ Where relationship lines crossed, and one of the connectors was
+ changed to <literal>Hidden</literal> or <literal>Draw
+ Split</literal>, the semi circle that indicated the previous
+ intersection was still shown on the remaining connector.
</para>
+
</message>
+
</logentry>
-
+
<logentry entrytype="bug">
+
<bugs>
- <fixes bugid="32734"/>
+ <fixes bugid="32734"/>
</bugs>
+
<versions>
- <version ver="5.0.15beta"/>
+ <version ver="5.0.15beta"/>
</versions>
+
<message>
+
<para>
- On an EER digram you could not select a
- relationship if the connection line wasn't stepped.
- You can now select a connector even if it
- is not stepped.
+ On an EER digram you could not select a relationship if the
+ connection line wasn't stepped. You can now select a connector
+ even if it is not stepped.
</para>
+
</message>
- </logentry>
-
+
+ </logentry>
+
<logentry entrytype="bug">
+
<bugs>
<fixes bugid="33263"/>
</bugs>
+
<versions>
<version ver="5.0.15beta"/>
</versions>
+
<message>
+
<para>
- The application crashed when attempting
- to export an SQL CREATE script.
+ The application crashed when attempting to export an SQL CREATE
+ script.
</para>
+
</message>
+
</logentry>
-
+
<logentry entrytype="bug">
+
<bugs>
<fixes bugid="34433"/>
</bugs>
+
<versions>
<version ver="5.0.15beta"/>
</versions>
+
<message>
+
<para>
- The <literal>Properties</literal> palette was
- not cleared when a new project was started. It
- retained the properties of the last selected object.
+ The <literal>Properties</literal> palette was not cleared when a
+ new project was started. It retained the properties of the last
+ selected object.
</para>
+
</message>
+
</logentry>
-
+
<logentry entrytype="bug">
+
<bugs>
<fixes bugid="34816"/>
</bugs>
+
<versions>
<version ver="5.0.15beta"/>
</versions>
+
<message>
+
<para>
- Attempting to move a table on an EER diagram after deleting
- a relationship, caused the application to crash.
+ Attempting to move a table on an EER diagram after deleting a
+ relationship, caused the application to crash.
</para>
+
</message>
+
</logentry>
-
+
<logentry entrytype="bug">
+
<bugs>
<fixes bugid="34987"/>
</bugs>
+
<versions>
<version ver="5.0.15beta"/>
</versions>
+
<message>
+
<para>
- After importing a DB Designer schema, the
- following error occurred:
- "Cairo error: input string not valid UTF-8."
+ After importing a DB Designer schema, the following error
+ occurred: "Cairo error: input string not valid UTF-8."
</para>
+
</message>
+
</logentry>
-
+
<logentry entrytype="bug">
+
<bugs>
<fixes bugid="34988"/>
</bugs>
+
<versions>
<version ver="5.0.15beta"/>
</versions>
+
<message>
+
<para>
- Scrollbar navigation did not work after importing
- a DB Designer schema with a large canvas size.
- However, you could still navigate using the
- <literal>Model Navigator</literal> palette.
+ Scrollbar navigation did not work after importing a DB Designer
+ schema with a large canvas size. However, you could still
+ navigate using the <literal>Model Navigator</literal> palette.
</para>
+
</message>
- </logentry>
-
+
+ </logentry>
+
<logentry entrytype="bug">
+
<bugs>
- <fixes bugid="34848"/>
+ <fixes bugid="34848"/>
<seealsobug bugid="34847"/>
</bugs>
+
<versions>
- <version ver="5.0.14abeta"/>
+ <version ver="5.0.14abeta"/>
</versions>
+
<message>
- <para>
- MWB files were not saved properly if Workbench crashed.
- Reopening such files caused Workbench to crash.
- </para>
+
+ <para>
+ MWB files were not saved properly if Workbench crashed.
+ Reopening such files caused Workbench to crash.
+ </para>
+
</message>
- </logentry>
-
+
+ </logentry>
+
<logentry entrytype="bug">
+
<bugs>
- <fixes bugid="34904"/>
+ <fixes bugid="34904"/>
</bugs>
+
<versions>
- <version ver="5.0.15beta"/>
+ <version ver="5.0.15beta"/>
</versions>
+
<message>
- <para>
- On the <literal>MySQL Model</literal> page, when the
- large icons view was selected, the <literal>Add Table</literal>
- icon disappeared.
- </para>
+
+ <para>
+ On the <literal>MySQL Model</literal> page, when the large icons
+ view was selected, the <literal>Add Table</literal> icon
+ disappeared.
+ </para>
+
</message>
- </logentry>
-
+
+ </logentry>
+
<logentry entrytype="bug">
+
<bugs>
- <fixes bugid="34934"/>
+ <fixes bugid="34934"/>
</bugs>
+
<versions>
- <version ver="5.0.15beta"/>
+ <version ver="5.0.15beta"/>
</versions>
+
<message>
- <para>
- Changing the <literal>drawSplit</literal> property of a connection
- from the <literal>Properties</literal> palette did not updated the
- <literal>Visibility</literal> section of the connection editor.
- </para>
+
+ <para>
+ Changing the <literal>drawSplit</literal> property of a
+ connection from the <literal>Properties</literal> palette did
+ not updated the <literal>Visibility</literal> section of the
+ connection editor.
+ </para>
+
</message>
- </logentry>
-
+
+ </logentry>
+
<logentry entrytype="bug">
+
<bugs>
- <fixes bugid="34847"/>
+ <fixes bugid="34847"/>
</bugs>
+
<versions>
- <version ver="5.0.14abeta"/>
+ <version ver="5.0.14abeta"/>
</versions>
+
<message>
- <para>
- Workbench models created in version 5.0.13
- crashed when used with version 5.0.14. The
- unscheduled Beta release, 5.0.14a fixes this bug.
- </para>
+
+ <para>
+ Workbench models created in version 5.0.13 crashed when used
+ with version 5.0.14. The unscheduled Beta release, 5.0.14a fixes
+ this bug.
+ </para>
+
</message>
- </logentry>
-
+
+ </logentry>
+
<logentry entrytype="bug">
+
<bugs>
- <fixes bugid="33588"/>
+ <fixes bugid="33588"/>
</bugs>
+
<versions>
- <version ver="5.0.14abeta"/>
+ <version ver="5.0.14abeta"/>
</versions>
+
<message>
- <para>
- Importing a DBDesigner file immediately threw an exception.
- This happened even when software rendering was used.
- DBDesigner files can now be imported without incident.
- </para>
+
+ <para>
+ Importing a DBDesigner file immediately threw an exception. This
+ happened even when software rendering was used. DBDesigner files
+ can now be imported without incident.
+ </para>
+
</message>
- </logentry>
-
+
+ </logentry>
+
<logentry entrytype="bug">
+
<bugs>
- <fixes bugid="34499"/>
+ <fixes bugid="34499"/>
</bugs>
+
<versions>
- <version ver="5.0.14abeta"/>
+ <version ver="5.0.14abeta"/>
</versions>
+
<message>
- <para>
- Repeatedly changing the object notation crashed Workbench.
- This is no longer repeatable.
- </para>
+
+ <para>
+ Repeatedly changing the object notation crashed Workbench. This
+ is no longer repeatable.
+ </para>
+
</message>
- </logentry>
-
+
+ </logentry>
+
<logentry entrytype="bug">
+
<bugs>
- <fixes bugid="34622"/>
+ <fixes bugid="34622"/>
</bugs>
+
<versions>
- <version ver="5.0.14abeta"/>
+ <version ver="5.0.14abeta"/>
</versions>
+
<message>
- <para>
- When clicking the <guibutton>Browse</guibutton> button
- in the image editor, the default file name was
- <literal>openFileDialog1</literal>.
- This now defaults to an empty string.
- </para>
+
+ <para>
+ When clicking the <guibutton>Browse</guibutton> button in the
+ image editor, the default file name was
+ <literal>openFileDialog1</literal>. This now defaults to an
+ empty string.
+ </para>
+
</message>
- </logentry>
-
+
+ </logentry>
+
<logentry entrytype="custom" customname="improvements"
customtitle="The following
improvements have been added to this version of Workbench:">
-
+
<versions>
<version ver="5.0.14beta"/>
</versions>
+
<message>
+
<para>
- The GRT inspector has been improved to support new types. Namely:
-
+ The GRT inspector has been improved to support new types.
+ Namely:
<itemizedlist>
+
<listitem>
<para>
text
</para>
</listitem>
+
<listitem>
<para>
longtext
</para>
</listitem>
+
<listitem>
<para>
bool
</para>
</listitem>
+
<listitem>
<para>
color
</para>
</listitem>
+
<listitem>
<para>
file
</para>
</listitem>
+
</itemizedlist>
-
- This makes it much easier to change
- object properties manually. Multiple selection support
- has also been improved — you can easily change a
- value for several selected objects at once.
+ This makes it much easier to change object properties manually.
+ Multiple selection support has also been improved — you
+ can easily change a value for several selected objects at once.
</para>
+
</message>
-
- </logentry>
-
+
+ </logentry>
+
<logentry entrytype="custom" customname="improvements"
customtitle="The following
improvements have been added to this version of Workbench:">
-
+
<versions>
<version ver="5.0.14beta"/>
</versions>
+
<message>
+
<para>
- Because of serious performance and display issues
- Workbench no longer uses Mesa. For those users who don't
- have native OpenGL support, Workbench now uses the
- Windows GDI API. The command line switch for using this
- mode is <option>-swrendering</option>. For more
- information about running Workbench from the command line
- see <xref linkend="wb-windows-running"/>.
+ Because of serious performance and display issues Workbench no
+ longer uses Mesa. For those users who don't have native OpenGL
+ support, Workbench now uses the Windows GDI API. The command
+ line switch for using this mode is
+ <option>-swrendering</option>. For more information about
+ running Workbench from the command line see
+ <xref linkend="wb-installing-windows-starting"/>.
</para>
+
</message>
-
+
</logentry>
-
+
<logentry entrytype="custom" customname="improvements"
customtitle="The following
improvements have been added to this version of Workbench:">
-
+
<versions>
<version ver="5.0.14beta"/>
</versions>
+
<message>
+
<para>
- An <guimenu>Export as SVG</guimenu> menu
- option has been added under the the <guimenu>File</guimenu>,
- <guimenu>Export</guimenu> menu option.
+ An <guimenu>Export as SVG</guimenu> menu option has been added
+ under the the <guimenu>File</guimenu>, <guimenu>Export</guimenu>
+ menu option.
</para>
+
</message>
-
+
</logentry>
-
-
+
<logentry entrytype="custom" customname="improvements"
customtitle="The following
improvements have been added to this version of Workbench:">
-
+
<versions>
<version ver="5.0.14beta"/>
</versions>
+
<message>
+
<para>
- A <guimenu>System Information</guimenu> menu
- option has been added to the <guimenu>Help</guimenu>
- menu. This option displays information
- about your system that is useful when reporting a big.
+ A <guimenu>System Information</guimenu> menu option has been
+ added to the <guimenu>Help</guimenu> menu. This option displays
+ information about your system that is useful when reporting a
+ big.
</para>
+
</message>
-
+
</logentry>
<logentry entrytype="custom" customname="improvements"
@@ -394,14 +1038,18 @@
<versions>
<version ver="5.0.14beta"/>
</versions>
+
<message>
+
<para>
- A <guimenu>Fit Objects to Contents</guimenu> option has been added under
- the <guimenu>Arrange</guimenu> menu option. This option expands an
- object on an EER diagram. For example, if a table has a long column name
- that is not fully displayed, using this menu option will expand the table
- making the column name visible.
- </para>
+ A <guimenu>Fit Objects to Contents</guimenu> option has been
+ added under the <guimenu>Arrange</guimenu> menu option. This
+ option expands an object on an EER diagram. For example, if a
+ table has a long column name that is not fully displayed, using
+ this menu option will expand the table making the column name
+ visible.
+ </para>
+
</message>
</logentry>
@@ -413,20 +1061,23 @@
<versions>
<version ver="5.0.14beta"/>
</versions>
+
<message>
+
<para>
- <guimenu>Expand All</guimenu> and <guimenu>Collapse All</guimenu>
- menu options have been added under the <guimenu>Arrange</guimenu> menu.
- The <guimenu>Expand All</guimenu> option expands
- all objects on an EER. This option will display a table's
- columns if the object notation supports expansion. Indexes will
- not automatically be expanded unless they were previously
- expanded and have been collapsed using the <guimenu>Collapse All</guimenu>
- menu option. Some object notations, such as
- <literal>Classic</literal>, do not allow for
- expansion or contraction. <guimenu>Collapse All</guimenu> undoes the operation
- performed by <guimenu>Expand All</guimenu>.
- </para>
+ <guimenu>Expand All</guimenu> and <guimenu>Collapse
+ All</guimenu> menu options have been added under the
+ <guimenu>Arrange</guimenu> menu. The <guimenu>Expand
+ All</guimenu> option expands all objects on an EER. This option
+ will display a table's columns if the object notation supports
+ expansion. Indexes will not automatically be expanded unless
+ they were previously expanded and have been collapsed using the
+ <guimenu>Collapse All</guimenu> menu option. Some object
+ notations, such as <literal>Classic</literal>, do not allow for
+ expansion or contraction. <guimenu>Collapse All</guimenu> undoes
+ the operation performed by <guimenu>Expand All</guimenu>.
+ </para>
+
</message>
</logentry>
@@ -672,13 +1323,12 @@
<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 when the <literal>expanded</literal> property
- is set to <literal>0</literal>.
+ 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 when the
+ <literal>expanded</literal> property is set to
+ <literal>0</literal>.
</para>
</message>
Modified: trunk/refman-common/connector-odbc.xml
===================================================================
--- trunk/refman-common/connector-odbc.xml 2008-03-15 12:16:43 UTC (rev 10257)
+++ trunk/refman-common/connector-odbc.xml 2008-03-15 12:32:38 UTC (rev 10258)
Changed blocks: 2, Lines Added: 11, Lines Deleted: 3; 1765 bytes
@@ -3841,7 +3841,14 @@
password with administrator privileges.
</para>
-<para>For correct operation of ODBC Administrator, you should ensure that the <filename>/Library/ODBC/odbc.ini</filename> file used to set up ODBC connectivity and DSNs are writable by the <literal>admin</literal> group. If this file is not writable by this group then the ODBC Administrator may fail, or may appear to have worked but not generated the correct entry.</para>
+ <para>
+ For correct operation of ODBC Administrator, you should ensure
+ that the <filename>/Library/ODBC/odbc.ini</filename> file used
+ to set up ODBC connectivity and DSNs are writable by the
+ <literal>admin</literal> group. If this file is not writable by
+ this group then the ODBC Administrator may fail, or may appear
+ to have worked but not generated the correct entry.
+ </para>
<warning>
<para>
@@ -3850,8 +3857,9 @@
this method. In this case you should use the command-line or
edit the <filename>odbc.ini</filename> file directly. Note
that existing DSNs or those that you create via the
- <command>myodbc3i</command> or <command>myodbc-installer</command>tool can still be checked and
- edited using ODBC Administrator.
+ <command>myodbc3i</command> or
+ <command>myodbc-installer</command>tool can still be checked
+ and edited using ODBC Administrator.
</para>
</warning>
Modified: trunk/workbench/Makefile.depends
===================================================================
--- trunk/workbench/Makefile.depends 2008-03-15 12:16:43 UTC (rev 10257)
+++ trunk/workbench/Makefile.depends 2008-03-15 12:32:38 UTC (rev 10258)
Changed blocks: 2, Lines Added: 0, Lines Deleted: 19; 1379 bytes
@@ -514,24 +514,6 @@
tutorial-manprepped.xml: $(tutorial_SOURCES) $(tutorial_IDMAPS)
tutorial-remprepped.xml: $(tutorial_SOURCES) $(tutorial_IDMAPS)
-uninstalling_INCLUDES = \
- ../common/fixedchars.ent \
- ../refman-common/urls.ent \
- all-entities.ent \
- version.ent \
- workbench.ent
-uninstalling_IMAGES =
-uninstalling_SOURCES = uninstalling.xml $(uninstalling_INCLUDES)
-uninstalling_IDMAPS =
-uninstalling.validpure: $(uninstalling_SOURCES)
-uninstalling.titles: $(uninstalling_SOURCES)
-uninstalling.useless: $(uninstalling_SOURCES)
-uninstalling.valid: $(uninstalling_SOURCES) $(uninstalling_IDMAPS)
-uninstalling.validwarn: $(uninstalling_SOURCES) $(uninstalling_IDMAPS)
-uninstalling-prepped.xml: $(uninstalling_SOURCES) $(uninstalling_IDMAPS)
-uninstalling-manprepped.xml: $(uninstalling_SOURCES) $(uninstalling_IDMAPS)
-uninstalling-remprepped.xml: $(uninstalling_SOURCES) $(uninstalling_IDMAPS)
-
validation_plugins_INCLUDES = \
../common/fixedchars.ent \
../refman-common/urls.ent \
@@ -629,7 +611,6 @@
tables.xml \
text-objects.xml \
tutorial.xml \
- uninstalling.xml \
validation-plugins.xml \
version.ent \
views.xml \
Modified: trunk/workbench/editions.xml
===================================================================
--- trunk/workbench/editions.xml 2008-03-15 12:16:43 UTC (rev 10257)
+++ trunk/workbench/editions.xml 2008-03-15 12:32:38 UTC (rev 10258)
Changed blocks: 3, Lines Added: 2, Lines Deleted: 10; 1099 bytes
@@ -9,10 +9,8 @@
<title>&workbench; Editions</title>
- <section id="wb-community-edition">
+ <para><emphasis role="bold">The Community Edition (OSS)</emphasis></para>
- <title>The Community Edition (OSS)</title>
-
<para>
The Community Edition is the foundation of all &workbench;
editions—versions that are currently available or those that
@@ -24,12 +22,8 @@
MySQL community.
</para>
- </section>
+ <para><emphasis role="bold">The Standard Edition</emphasis></para>
- <section id="wb-standard-edition">
-
- <title>The Standard Edition</title>
-
<para>
The Standard Edition is a commercial extension that builds on top
of the OSS Edition and adds modules and plugins, allowing for an
@@ -41,6 +35,4 @@
commercial edition can greatly improve your work flow.
</para>
- </section>
-
</chapter>
Modified: trunk/workbench/installing.xml
===================================================================
--- trunk/workbench/installing.xml 2008-03-15 12:16:43 UTC (rev 10257)
+++ trunk/workbench/installing.xml 2008-03-15 12:32:38 UTC (rev 10258)
Changed blocks: 2, Lines Added: 195, Lines Deleted: 153; 15456 bytes
@@ -9,150 +9,168 @@
<title>Installing &workbench;</title>
- <section id="wb-installation-requirements">
+ <para>
+ You can install &workbench; using with an installer or a Zip file.
+ The requirements for installing &workbench; are:
+ </para>
- <title>Requirements</title>
+ <orderedlist>
- <para>
- Currently, &workbench; is available for Windows only.
+ <listitem>
+ <para>
+ Currently, &workbench; is available for Windows only.
+ &workbench; runs on recent 32-bit Windows NT based operating
+ systems, including Windows XP, Vista, and Windows 2003. It
+ doesn't run on Windows 2000 and below.
<!--
The &workbench; requires the Java
Runtime Environment (JRE). The minimum version supported is 5.0
update 8.-->
- </para>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <literal>.Net 2.0 </literal> Framework is a requirement. If
+ you do not already have this framework installed, download it
+ <ulink url="http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=0856eacb-4362-4b0d-8edd-aab15c5e04f5">here</ulink>.
+ You may also need the <literal>VS2005.net
+ Redistributable</literal> but first try &workbench;. If the
+ application does not start download <literal>VS2005.net
+ Redistributable</literal>
+ <ulink url="http://www.microsoft.com/downloads/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&DisplayLang=en">here</ulink>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On start up, the application checks the OpenGL version and
+ selects between software and hardware rendering. To determine
+ the rendering method that is being used, open the
+ <guimenu>Help</guimenu> menu and choose the <guimenu>System
+ Info</guimenu> submenu.
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+ <section id="wb-installing-windows">
+
+ <title>Installing &workbench; on Windows</title>
+
<para>
- The <literal>.Net 2.0 </literal> Framework is a requirement. If
- you do not already have this framework installed, download it
- <ulink url="http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=0856eacb-4362-4b0d-8edd-aab15c5e04f5">here</ulink>.
- You may also need the <literal>VS2005.net
- Redistributable</literal> but first try &workbench;. If the
- application does not start download <literal>VS2005.net
- Redistributable</literal>
- <ulink url="http://www.microsoft.com/downloads/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&DisplayLang=en">here</ulink>.
+ &workbench; may be installed using the Windows installer file or
+ it may be installed manually from a ZIP file.
</para>
<para>
- On start up, the application checks the OpenGL version and selects
- between software and hardware rendering. To determine the rendering
- method that is being used, open the <guimenu>Help</guimenu> menu
- and choose the <guimenu>System Info</guimenu> submenu.
+ <emphasis role="bold">Installing &workbench; Using the
+ Installer</emphasis>
</para>
<para>
- &workbench; runs on recent 32-bit Windows NT based operating
- systems, including Windows XP, Vista, and Windows 2003. It doesn't
- run on Windows 2000 and below.
+ &workbench; can be installed using the Windows Installer
+ (<literal>.msi</literal>) installation package. The MSI package
+ bears the name
+ <literal>mysql-workbench-<replaceable>version</replaceable>-win32.msi</literal>,
+ where <replaceable>version</replaceable> indicates the &workbench;
+ version number.
</para>
- </section>
-
- <section id="wb-installation-windows">
-
- <title>Installing and Running &workbench; on Windows</title>
-
<para>
- &workbench; may be installed using the Windows installer file or
- it may be installed manually from a zipped file.
+ Improving the MySQL Installation Wizard depends on the support and
+ feedback of users. If you find that the MySQL Installation Wizard
+ is lacking some feature important to you, or if you discover a
+ bug, please report it in our bugs database. To do this use the
+ <guimenu>Report a Bug</guimenu> option under the
+ <guimenu>Help</guimenu> menu.
</para>
- <section id="wb-installation-windows-using-installer">
+ <orderedlist>
- <title>Installing &workbench; Using the Installer</title>
+ <listitem>
+ <para>
+ To install &workbench;, right click on the MSI file and select
+ the <guimenu>Install</guimenu> option from the pop-up menu.
+ </para>
- <para>
- &workbench; can be installed using the Windows Installer
- (<literal>.msi</literal>) installation package. The MSI package
- bears the name
- <literal>mysql-workbench-<replaceable>version</replaceable>-win32.msi</literal>,
- where <replaceable>version</replaceable> indicates the
- &workbench; version number.
- </para>
+ <important>
+ <para>
+ Installing &workbench; may require administrative
+ privileges.
+ </para>
+ </important>
+ </listitem>
- <para>
- Improving the MySQL Installation Wizard depends on the support
- and feedback of users like you. If you find that the MySQL
- Installation Wizard is lacking some feature important to you, or
- if you discover a bug, please report it in our bugs database. To
- do this use the <guimenu>Report a Bug</guimenu> option under the
- <guimenu>Help</guimenu> menu.
- </para>
+ <listitem>
+ <para>
+ At the <guilabel>Setup Type</guilabel> window you may choose a
+ <option>Complete</option> or <option>Custom</option>
+ installation. To use all features of &workbench; choose the
+ <option>Complete</option> option.
+ </para>
+ </listitem>
- <para>
- To install &workbench;, right click on the MSI file and select
- the <guimenu>Install</guimenu> option from the pop-up menu.
- </para>
-
- <note>
+ <listitem>
<para>
- Installing &workbench; on Windows Vista requires
- administrative privileges.
+ Unless you choose otherwise, &workbench; is installed in
+ <filename>C:\<replaceable>%PROGRAMFILES%</replaceable>\MySQL\MySQL
+ Workbench 5.0
+ <replaceable>edition_type</replaceable>\</filename>, where
+ <replaceable>%PROGRAMFILES%</replaceable> is the default
+ directory for programs for your locale. The
+ <literal>%PROGRAMFILES%</literal> directory may be
+ <filename>C:\Program Files</filename> or
+ <filename>C:\programme</filename>.
</para>
- </note>
+ </listitem>
- <para>
- At the <literal>Setup Type</literal> window you may choose a
- <option>complete</option> or <option>custom</option>
- installation. To use all features of &workbench; choose the
- <option>complete</option> option.
- </para>
+ </orderedlist>
- <para>
- Unless you choose otherwise, &workbench; is installed in
- <filename>C:\<replaceable>%PROGRAMFILES%</replaceable>\MySQL\MySQL
- Workbench 5.0
- <replaceable>edition_type</replaceable>\</filename>, where
- <replaceable>%PROGRAMFILES%</replaceable> is the default
- directory for programs for your locale. The
- <literal>%PROGRAMFILES%</literal> directory may be
- <filename>C:\Program Files</filename> or
- <filename>C:\programme</filename>.
- </para>
+ <para>
+ <emphasis role="bold">Installing From the ZIP File</emphasis>
+ </para>
- </section>
+ <para>
+ If you are having problems running the installer, as an
+ alternative, you can download a ZIP file without an installer.
+ That file is called
+ <literal>mysql-workbench-<replaceable>version</replaceable>-win32.zip</literal>.
+ Using a ZIP program, unpack it to the directory of your choice.
+ You may also want to create a shortcut on your desktop or the
+ quick launch bar.
+ </para>
- <section id="wb-installation-zip">
+ <para>
+ To install using the ZIP file, download the ZIP file to a
+ convenient location and decompress the file. You can place the
+ resulting directory anywhere on you system. You do not need to
+ install or configure the application before using it.
+ </para>
- <title>Installing From the ZIP File</title>
+ </section>
- <para>
- Download the zipped file to a convenient location and decompress
- it.
- </para>
+ <section id="wb-installing-windows-starting">
- <para>
- If you are having problems running the installer, as an
- alternative, you can download a ZIP file without an installer.
- That file is called
- <literal>mysql-workbench-<replaceable>version</replaceable>-win32.zip</literal>.
- Using a ZIP program, unpack it to the directory of your choice.
- You may also want to create a shortcut on your desktop or the
- quick launch bar.
- </para>
+ <title>Starting &workbench;</title>
- </section>
+ <para>
+ Installing &workbench; using the Windows installer automatically
+ creates two entries in the <guimenu>Start</guimenu> menu under
+ <guimenu>MySQL</guimenu>. If your graphic card does not support
+ OpenGL 1.5 select the <literal>Software Rendering</literal> menu
+ entry.
+ </para>
- <section id="wb-windows-running">
+ <para>
+ You may also start &workbench; from the command line. To view the
+ available command line options, issue the command
+ <command>MySQLWorkbench -help | more</command> from the
+ &workbench; installation directory. You should see the following
+ output:
+ </para>
- <title>Running &workbench;</title>
-
- <para>
- Installing &workbench; using the Windows installer automatically
- creates two entries in the <guimenu>Start</guimenu> menu under
- <guimenu>MySQL</guimenu>. If your graphic card does not support
- OpenGL 1.5 select the <literal>Software Rendering</literal> menu
- entry.
- </para>
-
- <para>
- You may also start &workbench; from the command line. To view
- the available command line options, issue the command
- <command>MySQLWorkbench -help | more</command> from the
- &workbench; installation directory. You should see the following
- output:
- </para>
-
<programlisting>
MySQL Workbench 5.0.14 SE Beta. (C) 2006-2008 by MySQL AB. All rights reserved.
@@ -168,71 +186,95 @@
-log ............ Instruction to save messages (other debug info) to file
</programlisting>
- <para>
- The &workbench; version number is displayed followed by a usage
- message and then the options. Use the
- <option>-swrendering</option> option if your video card does not
- support OpenGL 1.5. The <option>-version</option> option can be
- used to display the &workbench; version number or, optionally,
- the GRT shell version number. The other options are
- self-explanatory.
- </para>
+ <para>
+ The &workbench; version number is displayed followed by a usage
+ message and then the options. Use the
+ <option>-swrendering</option> option if your video card does not
+ support OpenGL 1.5. The <option>-version</option> option can be
+ used to display the &workbench; version number or, optionally, the
+ GRT shell version number. The other options are self-explanatory.
+ </para>
- <para>
- When using command line options that display output to a console
- window, namely <option>-help</option> and
- <option>-version</option>, be sure that you pipe the output
- through the <command>more</command> command otherwise nothing
- will be displayed.
- </para>
+ <para>
+ When using command line options that display output to a console
+ window, namely <option>-help</option> and
+ <option>-version</option>, be sure that you pipe the output
+ through the <command>more</command> command otherwise nothing will
+ be displayed.
+ </para>
- </section>
-
</section>
-<!--section id="wb-installing-unix">
+ <section id="wb-uninstalling-windows">
- <title>Installing &workbench; on Unix</title>
+ <title>Uninstalling &workbench; – Windows</title>
- <note>
- <para>
- The &workbench; is not currently available for Linux.
- </para>
- </note>
+ <para>
+ The method for uninstalling &workbench; will depend on how you
+ install &workbench; in the first place.
+ </para>
- <remark>
- [PL] When appropriate, add sections for other OSs as described in
- TOC.txt
- </remark>
+ <para>
+ <emphasis role="bold">Rmoving &workbench; when installed Using the
+ Installer</emphasis>
+ </para>
- <section id="wb-installation-unix-rpm">
+ <orderedlist>
- <title>Installation Using the RPM File</title>
+ <listitem>
+ <para>
+ To uninstall &workbench;, open the <guilabel>Control
+ Panel</guilabel> and Choose <guilabel>Add or Remove
+ Programs</guilabel>. Find the &workbench; entry and choose the
+ <guibutton>Remove</guibutton> button. Doing this will remove
+ &workbench;.
+ </para>
+ </listitem>
- <para></para>
+ <listitem>
+ <para>
+ Any modules added to the <filename>C:\Program
+ Files\MySQL\MySQL Workbench
+ <replaceable>version</replaceable>\modules</filename>
+ directory will <emphasis role="bold">not</emphasis> be
+ deleted.
+ </para>
+ </listitem>
- </section>
+ </orderedlist>
- <section id="wb-installation-unix-tarbal">
+ <note>
+ <para>
+ It is not possible to remove &workbench; from the command line
+ if you have installed &workbench; using the installer. Although
+ you can manually remove some of the compoentns There is no
+ command line option for removing &workbench;.
+ </para>
- <title>Installation Using the Tarball</title>
+ <para>
+ Removing the &workbench; directory manually will not remove all
+ the files belonging to &workbench;.
+ </para>
+ </note>
- <para></para>
+ <para>
+ <emphasis role="bold">When installed from a ZIP file</emphasis>
+ </para>
- </section>
+ <para>
+ If you installed &workbench; using a ZIP file, to remove
+ &workbench; you can just delete the &workbench; directory.
+ </para>
- </section>
-
- <section id="wb-installing-osx">
-
- <title>Installing &workbench; on Mac OS X</title>
-
<note>
<para>
- The &workbench; is not currently available for Mac OS X
+ If you installed any additional modules within the
+ <filename>modules</filename> directory and you want to keep
+ them, make sure you copy those modules to a different directory
+ before deleting the &workbench; directory.
</para>
</note>
- </section-->
+ </section>
</chapter>
Added: trunk/workbench/renamed-nodes.txt
===================================================================
--- trunk/workbench/renamed-nodes.txt (rev 0)
+++ trunk/workbench/renamed-nodes.txt 2008-03-15 12:32:38 UTC (rev 10258)
Changed blocks: 1, Lines Added: 30, Lines Deleted: 0; 1540 bytes
@@ -0,0 +1,30 @@
+# renamed-nodes.txt
+#
+# This file lists obsolete page IDs and map them onto the current pages.
+# It's used when a page ID changes or a page is removed and requests
+# for the old page need to be redirected.
+#
+# Syntax of each line is: old-name new-name [date]
+#
+# old-name is the original page ID. new-name is the new page ID.
+# The line causes requests for old-name.html to be mapped to new-name.html.
+# (Redirection is handled by the dev.mysql.com web server.)
+#
+# The date is optional. If given, it indicates when the mapping should
+# be considered "expired": Once the date has been reached, we generate
+# an error page, old-name.html, that is used for requests to the old
+# page, and that informs users of the URL for the new page. They must
+# then manually follow the link.
+#
+# Lines beginning with # in column one are interpreted as
+# comments and ignored.
+#
+wb-community-edition wb-editions
+wb-standard-edition wb-editions
+wb-installing-requirements wb-installing
+wb-installation-windows-using-installer wb-installing-windows
+wb-installation-zip wb-installing-windows
+wb-installation-windows wb-installing-windows
+wb-windows-running wb-installing-windows-starting
+wb-uninstall-windows-installer wb-uninstalling-windows
+wb-uninstall-windows-zip wb-uninstalling-windows
Modified: trunk/workbench/workbench.xml
===================================================================
--- trunk/workbench/workbench.xml 2008-03-15 12:16:43 UTC (rev 10257)
+++ trunk/workbench/workbench.xml 2008-03-15 12:32:38 UTC (rev 10258)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 2; 605 bytes
@@ -49,8 +49,6 @@
<xi:include href="installing.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
- <xi:include href="uninstalling.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-
<!--xi:include href="upgrading.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/-->
<!--xi:include href="initial-startup.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/-->
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10258 - in trunk: dynamic-docs/changelog refman-common workbench | mcbrown | 15 Mar |
