Author: mcbrown
Date: 2008-02-26 14:16:58 +0100 (Tue, 26 Feb 2008)
New Revision: 10014
Log:
Documenting Dev Bugs:
Bug #16653
Bug #28628
Bug #34271
Bug #32864
Bug #31959
Bug #29871
Bug #19065
Bug #29955
Bug #34395
Documenting Docs Bugs:
Bug #33941
Modified:
trunk/dynamic-docs/changelog/connector-net-versions.xml
trunk/dynamic-docs/changelog/connector-odbc-versions.xml
trunk/dynamic-docs/changelog/connector-odbc.xml
trunk/dynamic-docs/changelog/mysql-proxy-versions.xml
trunk/dynamic-docs/changelog/mysqld-1.xml
trunk/dynamic-docs/changelog/mysqld-versions.xml
trunk/dynamic-docs/changelog/vstudioplugin-versions.xml
trunk/dynamic-docs/changelog/vstudioplugin.xml
trunk/dynamic-docs/changelog/workbench-versions.xml
trunk/dynamic-docs/changelog/workbench.xml
trunk/refman-5.1/news-5.1-core.xml
trunk/refman-common/connector-odbc.xml
trunk/refman-common/news-cnet-core.xml
trunk/refman-common/news-codbc-core.xml
Modified: trunk/dynamic-docs/changelog/connector-net-versions.xml
===================================================================
--- trunk/dynamic-docs/changelog/connector-net-versions.xml 2008-02-26 00:15:08 UTC (rev 10013)
+++ trunk/dynamic-docs/changelog/connector-net-versions.xml 2008-02-26 13:16:58 UTC (rev 10014)
Changed blocks: 3, Lines Added: 2, Lines Deleted: 3; 1421 bytes
@@ -6,7 +6,6 @@
<versionentry ver="5.2.1" reldate="Not yet released"></versionentry>
<versionentry ver="5.2.0" reldate="Not yet released"></versionentry>
<versionentry ver="5.1.4" reldate="20 November 2007"></versionentry>
-
<versionentry ver="5.1.3" rellevel="beta" reldate="21 September 2007">
<versionentrypreamble>
@@ -46,7 +45,7 @@
</versionentry>
<versionentry ver="5.1.0" reldate="01 May 2007"/>
<versionentry ver="5.0.9" reldate="Not yet released"></versionentry>
- <versionentry ver="5.0.8" reldate="21 August 2007">
+ <versionentry ver="5.0.8" reldate="21 August 2007">
<versionentrypreamble>
@@ -80,7 +79,7 @@
<versionentry ver="5.0.0" reldate="08 August 2006"/>
<versionentry ver="1.0.11" reldate="Not yet released"/>
<versionentry ver="1.0.10" reldate="24 August 2007"/>
- <versionentry ver="1.0.9" reldate="02 February 2007"/>
+ <versionentry ver="1.0.9" reldate="02 February 2007"/>
<versionentry ver="1.0.8" reldate="20 October 2006"/>
<versionentry ver="1.0.7" reldate="21 November 2005"/>
<versionentry ver="1.0.6" reldate="03 October 2005"/>
Modified: trunk/dynamic-docs/changelog/connector-odbc-versions.xml
===================================================================
--- trunk/dynamic-docs/changelog/connector-odbc-versions.xml 2008-02-26 00:15:08 UTC (rev 10013)
+++ trunk/dynamic-docs/changelog/connector-odbc-versions.xml 2008-02-26 13:16:58 UTC (rev 10014)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 560 bytes
@@ -3,6 +3,7 @@
<versionlog>
<mysqlproductname title="MySQL Connector/ODBC"/>
+ <versionentry ver="5.1.3" reldate="Not yet released"></versionentry>
<versionentry ver="5.1.2" reldate="13 February 2008">
<versionentrypreamble>
Modified: trunk/dynamic-docs/changelog/connector-odbc.xml
===================================================================
--- trunk/dynamic-docs/changelog/connector-odbc.xml 2008-02-26 00:15:08 UTC (rev 10013)
+++ trunk/dynamic-docs/changelog/connector-odbc.xml 2008-02-26 13:16:58 UTC (rev 10014)
Changed blocks: 2, Lines Added: 161, Lines Deleted: 0; 3518 bytes
@@ -2,6 +2,166 @@
<!DOCTYPE changelog SYSTEM "changelog.dtd">
<changelog>
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="16653"/>
+ </bugs>
+
+ <versions>
+ <version ver="3.51.24"/>
+ </versions>
+
+ <message>
+
+ <para>
+ With some connections to MySQL databases using Connector/ODBC,
+ the connection would mistakenly report 'user cancelled' for
+ accesses to the database information.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes id="34271"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.3"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Descriptor records were not cleared correctly when calling
+ <literal>SQLFreeStmt(SQL_UNBIND)</literal>.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="32864"/>
+ </bugs>
+
+ <versions>
+ <version ver="3.51.24"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When using Crystal Reports, table and column names would be
+ truncated to 21 characters, and truncated columns in tables
+ where the truncated name was the duplicated would lead to only a
+ single column being displayed.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="feature">
+
+ <tags>
+ <highlight type="incompatiblechange"/>
+ </tags>
+
+ <versions>
+ <version ver="3.51.18"/>
+ </versions>
+
+ <message>
+
+ <para>
+ The <option>FLAG_DEBUG</option> option was removed.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="31959"/>
+ </bugs>
+
+ <versions>
+ <version ver="3.51.24"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When using the ODBC <literal>SQL_TXN_READ_COMMITTED</literal>
+ option, 'dirty' records would be read from tables as if the
+ option had not been applied.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
+ <fixes bugid="19065"/>
+ </bugs>
+
+ <versions>
+ <version ver="3.51.24"/>
+ <version ver="5.1.3"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Updating a <literal>RecordSet</literal> when the query involves
+ a <literal>BLOB</literal> field would fail.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="importantchange"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="29955"/>
+ </bugs>
+
+ <versions>
+ <version ver="3.51.24"/>
+ <version ver="5.1.3"/>
+ </versions>
+
+ <message>
+
+ <para>
+ In previous versions, the SSL certificate would automatically be
+ verified when used as part of the Connector/ODBC connection. The
+ default mode is now to ignore the verificate of certificates. To
+ enforce verification of the SSL certificate during connection,
+ use the <option>SSLVERIFY</option> DSN parameter, setting the
+ value to 1.
+ </para>
+
+ </message>
+
+ </logentry>
+
<logentry entrytype="platform">
<bugs>
@@ -1763,6 +1923,7 @@
<versions>
<version ver="3.51.21"/>
+ <version ver="3.51.24"/>
</versions>
<message>
Modified: trunk/dynamic-docs/changelog/mysql-proxy-versions.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysql-proxy-versions.xml 2008-02-26 00:15:08 UTC (rev 10013)
+++ trunk/dynamic-docs/changelog/mysql-proxy-versions.xml 2008-02-26 13:16:58 UTC (rev 10014)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 3; 581 bytes
@@ -3,11 +3,8 @@
<versionlog>
<mysqlproductname title="MySQL Proxy"/>
-
<versionentry ver="0.6.0" reldate="Not yet released"/>
-
<versionentry ver="0.5.1" reldate="30 June 2007"/>
-
<versionentry ver="0.5.0" reldate="19 June 2007">
<versionentrypreamble>
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-02-26 00:15:08 UTC (rev 10013)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-02-26 13:16:58 UTC (rev 10014)
Changed blocks: 1, Lines Added: 62, Lines Deleted: 0; 1904 bytes
@@ -9,6 +9,68 @@
<logentry entrytype="bug">
<tags>
+ <manual type="Windows"/>
+ <manual type="Config Wizard"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="28628"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23"/>
+ <version ver="5.0.51a"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When running the MySQL Instance Configuration Wizard, a race
+ condition could exist that would fail to connect to a newly
+ configured instance. This was because <command>mysqld</command>
+ had not completed the startup process before the next stage of
+ the installation process.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="Maria"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="34395"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.24-maria"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When creating tables not using the <literal>MARIA</literal>
+ engine, it would be possible to create a table using the
+ <literal>TRANSACTIONAL</literal> option, even though this option
+ is not supported by non-<literal>MARIA</literal> tables. A
+ warning will now be produced when using these options, but the
+ option will still be recorded within the options for the table
+ to allow for correct modification during <literal>ALTER
+ TABLE</literal> operations.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
<highlight type="cluster"/>
<manual type="icc"/>
<manual type="IA64"/>
Modified: trunk/dynamic-docs/changelog/mysqld-versions.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-versions.xml 2008-02-26 00:15:08 UTC (rev 10013)
+++ trunk/dynamic-docs/changelog/mysqld-versions.xml 2008-02-26 13:16:58 UTC (rev 10014)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 0; 975 bytes
@@ -25,6 +25,18 @@
<versionentry ver="5.2.3" reldate="15 February 2007"/>
<versionentry ver="5.2.2" reldate="Not released"/>
<versionentry ver="5.2.1" reldate="Not released"/>
+ <versionentry ver="5.1.24-maria" reldate="Not yet released">
+
+ <versionentrypreamble>
+
+ <para>
+ The following changes apply only to builds of MySQL 5.1.24 that
+ include the <literal>MARIA</literal> storage engine.
+ </para>
+
+ </versionentrypreamble>
+
+ </versionentry>
<versionentry ver="5.1.24" reldate="Not yet released"/>
<versionentry ver="5.1.23" reldate="29 January 2008"/>
<versionentry ver="5.1.23" subver="ndb-6.3.11" reldate="Not yet released"/>
Modified: trunk/dynamic-docs/changelog/vstudioplugin-versions.xml
===================================================================
--- trunk/dynamic-docs/changelog/vstudioplugin-versions.xml 2008-02-26 00:15:08 UTC (rev 10013)
+++ trunk/dynamic-docs/changelog/vstudioplugin-versions.xml 2008-02-26 13:16:58 UTC (rev 10014)
Changed blocks: 4, Lines Added: 0, Lines Deleted: 8; 1652 bytes
@@ -3,11 +3,8 @@
<versionlog>
<mysqlproductname title="MySQL Visual Studio Plugin"/>
-
<versionentry ver="1.0.3" reldate="Not yet released"/>
-
<versionentry ver="1.0.2" reldate="Not yet released"/>
-
<versionentry ver="1.0.1" reldate="4 October 2006">
<versionentrypreamble>
@@ -16,7 +13,6 @@
This is a bug fix release to resolve an incompatibility issue
with Connector/NET 5.0.1.
</para>
-
<para>
It is critical that this release only be used with Connector/NET
5.0.1. After installing Connector/NET 5.0.1, you will need to
@@ -27,15 +23,12 @@
folder). Near the bottom of the file you will see a line like
this:
</para>
-
<programlisting><add name="MySQL Data Provider" invariant="MySql.Data.MySqlClient"
description=".Net Framework Data Provider for MySQL"
type="MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data"/></programlisting>
-
<para>
It needs to be changed to be like this:
</para>
-
<programlisting><add name="MySQL Data Provider" invariant="MySql.Data.MySqlClient"
description=".Net Framework Data Provider for MySQL"
type="MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data,
@@ -45,7 +38,6 @@
</versionentrypreamble>
</versionentry>
-
<versionentry ver="1.0.0" reldate="4 October 2006"/>
</versionlog>
Modified: trunk/dynamic-docs/changelog/vstudioplugin.xml
===================================================================
--- trunk/dynamic-docs/changelog/vstudioplugin.xml 2008-02-26 00:15:08 UTC (rev 10013)
+++ trunk/dynamic-docs/changelog/vstudioplugin.xml 2008-02-26 13:16:58 UTC (rev 10014)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 616 bytes
@@ -106,8 +106,8 @@
<message>
<para>
- Running queries based on a stored procedure would cause the
- data set designer to terminate. (Bugs #26364)
+ Running queries based on a stored procedure would cause the data
+ set designer to terminate. (Bugs #26364)
</para>
</message>
Modified: trunk/dynamic-docs/changelog/workbench-versions.xml
===================================================================
--- trunk/dynamic-docs/changelog/workbench-versions.xml 2008-02-26 00:15:08 UTC (rev 10013)
+++ trunk/dynamic-docs/changelog/workbench-versions.xml 2008-02-26 13:16:58 UTC (rev 10014)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 13; 1040 bytes
@@ -3,29 +3,27 @@
<versionlog>
<mysqlproductname title="MySQL Workbench"/>
-
- <versionentry ver="5.0.14beta" reldate="25 February 2008">
-
+ <versionentry ver="5.0.14beta" reldate="25 February 2008">
+
<versionentrypreamble>
<para>
- <!--Not used but could add notes here-->
+<!--Not used but could add notes here-->
</para>
</versionentrypreamble>
-
- </versionentry>
-
+
+ </versionentry>
<versionentry ver="5.0.15beta" reldate="Not yet released">
-
+
<versionentrypreamble>
-
+
<para>
- <!--Not used but could add notes here-->
+<!--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-26 00:15:08 UTC (rev 10013)
+++ trunk/dynamic-docs/changelog/workbench.xml 2008-02-26 13:16:58 UTC (rev 10014)
Changed blocks: 2, Lines Added: 274, Lines Deleted: 138; 19582 bytes
@@ -5,8 +5,8 @@
%all.entities;
]>
<changelog>
-
- <!--logentry entrytype="bug">
+
+<!--logentry entrytype="bug">
<bugs>
<fixes bugid=""/>
</bugs>
@@ -19,455 +19,591 @@
</para>
</message>
</logentry-->
-
+
<logentry entrytype="bug">
+
<bugs>
- <fixes bugid="34601"/>
+ <fixes bugid="34601"/>
</bugs>
+
<versions>
- <version ver="5.0.14beta"/>
+ <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>
+
+ <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.
+ 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.
+ 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:
-
+ 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>
+ <para></para>
</listitem>
+
<listitem>
<para>
- Column definitions that are long relative to the table name,
- are truncated.
+ 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.
+ 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.
+ 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.
+ 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.
+ 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.
+ 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.
+ 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.
+ 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>.
+ 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
+ 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.
+ 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.
+ 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>
<fixes bugid="34536"/>
</bugs>
+
<versions>
<version ver="5.0.14beta"/>
</versions>
+
<message>
+
<para>
- When there were multiple tables with long identifiers
- the <literal>Physical Schemata</literal> section
- of the <literal>MySQL Model</literal> page was messy.
- Table names were obscured and sometimes overlapped.
- Also, the position of the <literal>Add Table</literal> icon
- was not optimal. Now the space between table
- names is adjusted to the largest entry and the
+ When there were multiple tables with long identifiers the
+ <literal>Physical Schemata</literal> section of the
+ <literal>MySQL Model</literal> page was messy. Table names were
+ obscured and sometimes overlapped. Also, the position of the
+ <literal>Add Table</literal> icon was not optimal. Now the space
+ between table names is adjusted to the largest entry and the
<literal>Add Table</literal> icon is fixed in the upper left
corner.
</para>
+
</message>
+
</logentry>
<logentry entrytype="bug">
+
<bugs>
<fixes bugid="32578"/>
</bugs>
+
<versions>
<version ver="5.0.14beta"/>
</versions>
+
<message>
+
<para>
- When forward engineering to a live database, objects
- not selected on the <literal>Select Objects</literal> page
- were still created. This applied to tables, routines, and
- users.
- </para>
+ When forward engineering to a live database, objects not
+ selected on the <literal>Select Objects</literal> page were
+ still created. This applied to tables, routines, and users.
+ </para>
+
</message>
+
</logentry>
<logentry entrytype="bug">
+
<bugs>
<fixes bugid="34503"/>
</bugs>
+
<versions>
<version ver="5.0.14beta"/>
</versions>
+
<message>
+
<para>
When returning to the <literal>SQL Export Filter</literal> page
- after using the <guibutton>Back</guibutton> button,
- filters were no longer selected.
- Selections now persist.
- </para>
+ after using the <guibutton>Back</guibutton> button, filters were
+ no longer selected. Selections now persist.
+ </para>
+
</message>
+
</logentry>
<logentry entrytype="bug">
+
<bugs>
<fixes bugid="34501"/>
</bugs>
+
<versions>
<version ver="5.0.14beta"/>
</versions>
+
<message>
+
<para>
- The export filters were applied more than once
- when forward engineering an SQL <literal>CREATE</literal> script.
- This happened if you exported the script after
- using the <guibutton>Back</guibutton>
- button on the <literal>SQL Export Filter</literal> page.
- </para>
+ The export filters were applied more than once when forward
+ engineering an SQL <literal>CREATE</literal> script. This
+ happened if you exported the script after using the
+ <guibutton>Back</guibutton> button on the <literal>SQL Export
+ Filter</literal> page.
+ </para>
+
</message>
+
</logentry>
<logentry entrytype="bug">
+
<bugs>
<fixes bugid="34206"/>
</bugs>
+
<versions>
<version ver="5.0.14beta"/>
</versions>
+
<message>
+
<para>
- Creating a new foreign key did not update
- an EER diagram. An EER diagram is now
- updated immediately.
+ Creating a new foreign key did not update an EER diagram. An EER
+ diagram is now updated immediately.
</para>
+
</message>
+
</logentry>
<logentry entrytype="bug">
+
<bugs>
<fixes bugid="34434"/>
</bugs>
+
<versions>
<version ver="5.0.14beta"/>
</versions>
+
<message>
+
<para>
- When multiple objects on an EER diagram were selected and
- deleted, Workbench crashed. This happened when both connections and
- tables were selected.
+ When multiple objects on an EER diagram were selected and
+ deleted, Workbench crashed. This happened when both connections
+ and tables were selected.
</para>
+
</message>
+
</logentry>
<logentry entrytype="bug">
+
<bugs>
<fixes bugid="34342"/>
</bugs>
+
<versions>
<version ver="5.0.14beta"/>
</versions>
+
<message>
+
<para>
- Users failed to be created
- when exporting an SQL <literal>CREATE</literal> script.
+ Users failed to be created when exporting an SQL
+ <literal>CREATE</literal> script.
</para>
+
</message>
+
</logentry>
<logentry entrytype="bug">
+
<bugs>
<fixes bugid="34230"/>
</bugs>
+
<versions>
<version ver="5.0.14beta"/>
</versions>
+
<message>
+
<para>
Copying a table from the <literal>MySQL Model</literal> page to
- an EER diagram canvas created a duplicate table
- with the same name as the
- original. This table did not show up in the <literal>Catalog</literal>
- palette or in the appropriate schema in the<literal>Physical Schemata</literal>
- section of the <literal>MySQL Model</literal> page.
+ an EER diagram canvas created a duplicate table with the same
+ name as the original. This table did not show up in the
+ <literal>Catalog</literal> palette or in the appropriate schema
+ in the<literal>Physical Schemata</literal> section of the
+ <literal>MySQL Model</literal> page.
</para>
+
</message>
+
</logentry>
<logentry entrytype="bug">
+
<bugs>
<fixes bugid="33139"/>
</bugs>
+
<versions>
<version ver="5.0.14beta"/>
</versions>
+
<message>
+
<para>
- When changing the foreign key column of a table on an
- EER diagram, the foreign key did not change color and
- Workbench crashed when attempting to save the MWB file.
- The application no longer crashes and the foreign key is updated.
+ When changing the foreign key column of a table on an EER
+ diagram, the foreign key did not change color and Workbench
+ crashed when attempting to save the MWB file. The application no
+ longer crashes and the foreign key is updated.
</para>
+
</message>
+
</logentry>
<logentry entrytype="bug">
+
<bugs>
<fixes bugid="34496"/>
</bugs>
+
<versions>
<version ver="5.0.14beta"/>
</versions>
+
<message>
- <para>
- When the object notation was Workbench Classic
- the width of a table on an EER diagram could not
- be less than the widest column. If there was an enum column
- with many options, this made for a
- disproportionately wide table. Table width can now be less
+
+ <para>
+ When the object notation was Workbench Classic the width of a
+ table on an EER diagram could not be less than the widest
+ column. If there was an enum column with many options, this made
+ for a disproportionately wide table. Table width can now be less
than the widest column.
</para>
+
</message>
+
</logentry>
<logentry entrytype="bug">
+
<bugs>
<fixes bugid="34396"/>
</bugs>
+
<versions>
<version ver="5.0.14beta"/>
</versions>
+
<message>
- <para>
- When using the menu option <guimenu>Generate Schema Diff Report</guimenu>
- an exception was thrown. A new tree-less version of the Diff
- report plugin resolves this problem.
+
+ <para>
+ When using the menu option <guimenu>Generate Schema Diff
+ Report</guimenu> an exception was thrown. A new tree-less
+ version of the Diff report plugin resolves this problem.
</para>
+
</message>
+
</logentry>
</changelog>
Modified: trunk/refman-5.1/news-5.1-core.xml
===================================================================
--- trunk/refman-5.1/news-5.1-core.xml 2008-02-26 00:15:08 UTC (rev 10013)
+++ trunk/refman-5.1/news-5.1-core.xml 2008-02-26 13:16:58 UTC (rev 10014)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 665 bytes
@@ -37,6 +37,14 @@
<filename>refman-common</filename> directory.
</remark>
+ <section id="news-5-1-24-maria">
+
+ <title condition="dynamic:changelog:vertitle" role="5.1.24-maria:mysqld:all"/>
+
+ <para condition="dynamic:changelog:entrylist" role="5.1.24-maria:mysqld:all"/>
+
+ </section>
+
<section id="news-5-1-24">
<title condition="dynamic:changelog:vertitle" role="5.1.24:mysqld:all"/>
Modified: trunk/refman-common/connector-odbc.xml
===================================================================
--- trunk/refman-common/connector-odbc.xml 2008-02-26 00:15:08 UTC (rev 10013)
+++ trunk/refman-common/connector-odbc.xml 2008-02-26 13:16:58 UTC (rev 10014)
Changed blocks: 2, Lines Added: 5, Lines Deleted: 1; 1297 bytes
@@ -2783,6 +2783,10 @@
<entry/>
<entry>The character set to use for the connection. Added in 3.51.17.</entry>
</row>
+ <row><entry><literal>sslverify</literal></entry>
+ <entry/>
+ <entry>If set to 1, the SSL certificate will be verified when used with the MySQL connection. If not set, then the default behaviour is to ignore SSL certificate verification. </entry>
+ </row>
</tbody>
</tgroup>
</informaltable>
@@ -2839,7 +2843,7 @@
<entry><literal>FLAG_DEBUG</literal></entry>
<entry>Trace Driver Calls To myodbc.log</entry>
<entry>Make a debug log in <filename>C:\myodbc.log</filename> on Windows, or
- <filename>/tmp/myodbc.log</filename> on Unix variants.</entry>
+ <filename>/tmp/myodbc.log</filename> on Unix variants. This option was removed in Connector/ODBC 3.51.18.</entry>
</row>
<row>
<entry>8</entry>
Modified: trunk/refman-common/news-cnet-core.xml
===================================================================
--- trunk/refman-common/news-cnet-core.xml 2008-02-26 00:15:08 UTC (rev 10013)
+++ trunk/refman-common/news-cnet-core.xml 2008-02-26 13:16:58 UTC (rev 10014)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 685 bytes
@@ -19,6 +19,14 @@
<remark role="dynamic-dependency-list"/>
+ <section id="connector-net-news-5-2-1">
+
+ <title condition="dynamic:changelog:vertitle" role="5.2.1:connector-net:all"/>
+
+ <para condition="dynamic:changelog:entrylist" role="5.2.1:connector-net:all"/>
+
+ </section>
+
<section id="connector-net-news-5-2-0">
<title condition="dynamic:changelog:vertitle" role="5.2.0:connector-net:all"/>
Modified: trunk/refman-common/news-codbc-core.xml
===================================================================
--- trunk/refman-common/news-codbc-core.xml 2008-02-26 00:15:08 UTC (rev 10013)
+++ trunk/refman-common/news-codbc-core.xml 2008-02-26 13:16:58 UTC (rev 10014)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 677 bytes
@@ -18,6 +18,14 @@
<remark role="dynamic-dependency-list"/>
+ <section id="myodbc-news-5-1-3">
+
+ <title condition="dynamic:changelog:vertitle" role="5.1.3:connector-odbc:all"/>
+
+ <para condition="dynamic:changelog:entrylist" role="5.1.3:connector-odbc:all"/>
+
+ </section>
+
<section id="myodbc-news-5-1-2">
<title condition="dynamic:changelog:vertitle" role="5.1.2:connector-odbc:all"/>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10014 - in trunk: dynamic-docs/changelog refman-5.1 refman-common | mcbrown | 26 Feb |
