Below is the list of changes that have just been committed into a local
mysqldoc repository of paul. When paul does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html
ChangeSet
1.3021 05/07/14 14:01:03 paul@stripped +3 -0
Document bugfix. (Bug #9358)
Document bugfix. (Bug #9558)
Document bugfix. (Bug #10651)
Document bugfix. (Bug #10927)
Document bugfix. (Bug #11044)
Document bugfix. (Bug #11635)
Document bugfix. (Bug #11678)
refman/news.xml
1.70 05/07/14 14:01:02 paul@stripped +81 -13
Document bugfix. (Bug #9358)
Document bugfix. (Bug #9558)
Document bugfix. (Bug #10651)
Document bugfix. (Bug #10927)
Document bugfix. (Bug #11044)
Document bugfix. (Bug #11635)
Document bugfix. (Bug #11678)
refman-5.0/news.xml
1.58 05/07/14 14:01:02 paul@stripped +40 -0
Sync.
refman-4.1/news.xml
1.49 05/07/14 14:01:02 paul@stripped +42 -16
Sync.
# This is a BitKeeper patch. What follows are the unified diffs for the
# set of deltas contained in the patch. The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User: paul
# Host: kite-hub.kitebird.com
# Root: /src/extern/MySQL/bk/mysqldoc
--- 1.48/refman-4.1/news.xml 2005-07-14 11:49:18 -05:00
+++ 1.49/refman-4.1/news.xml 2005-07-14 14:01:02 -05:00
@@ -182,9 +182,7 @@
Functionality added or changed:
</para>
- <itemizedlist>
-
- </itemizedlist>
+ <itemizedlist></itemizedlist>
<para>
Bugs fixed:
@@ -237,19 +235,6 @@
</para></listitem>
<listitem><para>
- Corrected an optimization failure where a query returned an
- incorrect result for use of a newly populated table until the table
- was flushed. (Bug #11700)
- </para></listitem>
-
- <listitem><para>
- Modifying a <literal>CHAR</literal> column with the
- <literal>utf8</literal> character set to a shorter length did not
- properly truncate values due to not computing their length in
- <literal>utf8</literal> character units. (Bug #11591)
- </para></listitem>
-
- <listitem><para>
<literal>MEMORY</literal> tables now support indexes of up to 500
bytes. See <xref linkend="memory-storage-engine"/>. (Bug #10566)
</para></listitem>
@@ -320,6 +305,47 @@
<!-- NOTE: No need to start every item with "Fixed..."; sufficient to
describe the issue that was fixed. Use past tense. -->
+
+ <listitem><para>
+ <command>mysqldump</command> could crash for illegal or nonexistent
+ table names. (Bug #9358)
+ </para></listitem>
+
+ <listitem><para>
+ The <option>--no-data</option> option for
+ <command>mysqldump</command> was being ignored if table names were
+ given after the database name. (Bug #9558)
+ </para></listitem>
+
+ <listitem><para>
+ <command>mysqldump</command> now exports <literal>HASH</literal>
+ index definitions using <literal>USING</literal> rather than
+ <literal>TYPE</literal> when the index name is optional. This
+ corrects a problem when reloading the output for <literal>PRIMARY
+ KEY</literal> definition, because <literal>TYPE</literal> must be
+ preceded an index name, which is not given for a <literal>PRIMARY
+ KEY</literal>. (Bug #11635)
+ </para></listitem>
+
+ <listitem><para>
+ The <option>--master-data</option> option for
+ <command>mysqldump</command> resulted in no error if the binary log
+ was not enabled. Now an error occurs unless the
+ <option>--force</option> option is given. (Bug #11678)
+ </para></listitem>
+
+ <listitem><para>
+ Corrected an optimization failure where a query returned an
+ incorrect result for use of a newly populated table until the table
+ was flushed. (Bug #11700)
+ </para></listitem>
+
+ <listitem><para>
+ Modifying a <literal>CHAR</literal> column with the
+ <literal>utf8</literal> character set to a shorter length did not
+ properly truncate values due to not computing their length in
+ <literal>utf8</literal> character units. (Bug #11591)
+ </para></listitem>
<listitem><para>
<literal>DES_ENCRYPT()</literal> and
--- 1.57/refman-5.0/news.xml 2005-07-14 11:49:11 -05:00
+++ 1.58/refman-5.0/news.xml 2005-07-14 14:01:02 -05:00
@@ -411,6 +411,39 @@
<itemizedlist>
<listitem><para>
+ Instances of the <literal>VAR_SAMP()</literal> function in view
+ definitions were converted to <literal>VARIANCE()</literal>. This
+ is incorrect because <literal>VARIANCE()</literal> is the same as
+ <literal>VAR_POP()</literal>, not <literal>VAR_SAMP()</literal>.
+ (Bug #10651)
+ </para></listitem>
+
+ <listitem><para>
+ <command>mysqldump</command> failed when reloading a view if the
+ view was defined in terms of a different view that had not yet been
+ reloaded. <command>mysqldump</command> now creates a dummy table to
+ handle this case. (Bug #10927)
+ </para></listitem>
+
+ <listitem><para>
+ <command>mysqldump</command> could crash for illegal or nonexistent
+ table names. (Bug #9358)
+ </para></listitem>
+
+ <listitem><para>
+ The <option>--no-data</option> option for
+ <command>mysqldump</command> was being ignored if table names were
+ given after the database name. (Bug #9558)
+ </para></listitem>
+
+ <listitem><para>
+ The <option>--master-data</option> option for
+ <command>mysqldump</command> resulted in no error if the binary log
+ was not enabled. Now an error occurs unless the
+ <option>--force</option> option is given. (Bug #11678)
+ </para></listitem>
+
+ <listitem><para>
<literal>DES_ENCRYPT()</literal> and
<literal>DES_DECRYPT()</literal> require SSL support to be enabled,
but were not checking for it. Checking for incorrect arguments or
@@ -771,6 +804,13 @@
thought to be fixed previously, it was later discovered to be
present in the MySQL 5.0.7-beta release for Windows. (Bug #9148,
<ulink url="http://cve.mitre.org/cvename.cgi?name=CAN-2005-0799">CAN-2005-0799</ulink>
+ </para></listitem>
+
+ <listitem><para>
+ <literal>SELECT DISTINCT</literal> queries or <literal>GROUP
+ BY</literal> queries without <literal>MIN()</literal> or
+ <literal>MAX()</literal> could return inconsistent results for
+ indexed columns. (Bug #11044)
</para></listitem>
<listitem><para>
--- 1.69/refman/news.xml 2005-07-14 11:48:09 -05:00
+++ 1.70/refman/news.xml 2005-07-14 14:01:02 -05:00
@@ -403,6 +403,39 @@
<itemizedlist>
<listitem><para>
+ Instances of the <literal>VAR_SAMP()</literal> function in view
+ definitions were converted to <literal>VARIANCE()</literal>. This
+ is incorrect because <literal>VARIANCE()</literal> is the same as
+ <literal>VAR_POP()</literal>, not <literal>VAR_SAMP()</literal>.
+ (Bug #10651)
+ </para></listitem>
+
+ <listitem><para>
+ <command>mysqldump</command> failed when reloading a view if the
+ view was defined in terms of a different view that had not yet been
+ reloaded. <command>mysqldump</command> now creates a dummy table to
+ handle this case. (Bug #10927)
+ </para></listitem>
+
+ <listitem><para>
+ <command>mysqldump</command> could crash for illegal or nonexistent
+ table names. (Bug #9358)
+ </para></listitem>
+
+ <listitem><para>
+ The <option>--no-data</option> option for
+ <command>mysqldump</command> was being ignored if table names were
+ given after the database name. (Bug #9558)
+ </para></listitem>
+
+ <listitem><para>
+ The <option>--master-data</option> option for
+ <command>mysqldump</command> resulted in no error if the binary log
+ was not enabled. Now an error occurs unless the
+ <option>--force</option> option is given. (Bug #11678)
+ </para></listitem>
+
+ <listitem><para>
<literal>DES_ENCRYPT()</literal> and
<literal>DES_DECRYPT()</literal> require SSL support to be enabled,
but were not checking for it. Checking for incorrect arguments or
@@ -766,6 +799,13 @@
</para></listitem>
<listitem><para>
+ <literal>SELECT DISTINCT</literal> queries or <literal>GROUP
+ BY</literal> queries without <literal>MIN()</literal> or
+ <literal>MAX()</literal> could return inconsistent results for
+ indexed columns. (Bug #11044)
+ </para></listitem>
+
+ <listitem><para>
The <literal>SHOW INSTANCE OPTIONS</literal> command in MySQL
Instance Manager displayed option values incorrectly for options
for which no value had been given. (Bug #11200)
@@ -5016,19 +5056,6 @@
</para></listitem>
<listitem><para>
- Corrected an optimization failure where a query returned an
- incorrect result for use of a newly populated table until the table
- was flushed. (Bug #11700)
- </para></listitem>
-
- <listitem><para>
- Modifying a <literal>CHAR</literal> column with the
- <literal>utf8</literal> character set to a shorter length did not
- properly truncate values due to not computing their length in
- <literal>utf8</literal> character units. (Bug #11591)
- </para></listitem>
-
- <listitem><para>
<literal>MEMORY</literal> tables now support indexes of up to 500
bytes. See <xref linkend="memory-storage-engine"/>. (Bug #10566)
</para></listitem>
@@ -5108,6 +5135,47 @@
describe the issue that was fixed. Use past tense. -->
<itemizedlist>
+
+ <listitem><para>
+ <command>mysqldump</command> could crash for illegal or nonexistent
+ table names. (Bug #9358)
+ </para></listitem>
+
+ <listitem><para>
+ The <option>--no-data</option> option for
+ <command>mysqldump</command> was being ignored if table names were
+ given after the database name. (Bug #9558)
+ </para></listitem>
+
+ <listitem><para>
+ <command>mysqldump</command> now exports <literal>HASH</literal>
+ index definitions using <literal>USING</literal> rather than
+ <literal>TYPE</literal> when the index name is optional. This
+ corrects a problem when reloading the output for <literal>PRIMARY
+ KEY</literal> definition, because <literal>TYPE</literal> must be
+ preceded an index name, which is not given for a <literal>PRIMARY
+ KEY</literal>. (Bug #11635)
+ </para></listitem>
+
+ <listitem><para>
+ The <option>--master-data</option> option for
+ <command>mysqldump</command> resulted in no error if the binary log
+ was not enabled. Now an error occurs unless the
+ <option>--force</option> option is given. (Bug #11678)
+ </para></listitem>
+
+ <listitem><para>
+ Corrected an optimization failure where a query returned an
+ incorrect result for use of a newly populated table until the table
+ was flushed. (Bug #11700)
+ </para></listitem>
+
+ <listitem><para>
+ Modifying a <literal>CHAR</literal> column with the
+ <literal>utf8</literal> character set to a shorter length did not
+ properly truncate values due to not computing their length in
+ <literal>utf8</literal> character units. (Bug #11591)
+ </para></listitem>
<listitem><para>
<literal>DES_ENCRYPT()</literal> and
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (paul:1.3021) | paul | 14 Jul |
