Below is the list of changes that have just been committed into a local
mysqldoc repository of jon. When jon 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.2896 05/06/29 00:34:53 jon@stripped +3 -0
Documented bugfixes:
Bug#10178
Bug#11122
(Sync refman-4.1 and refman-5.0 to refman.)
refman/news.xml
1.36 05/06/29 00:34:51 jon@stripped +85 -46
Documented bugfixes:
Bug#10178
Bug#11122
refman-5.0/news.xml
1.31 05/06/29 00:34:51 jon@stripped +85 -46
Documented bugfixes:
Bug#10178
Bug#11122
(Sync to refman.)
refman-4.1/news.xml
1.31 05/06/29 00:34:51 jon@stripped +85 -46
Documented bugfixes:
Bug#10178
Bug#11122
(Sync to refman.)
# 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: jon
# Host: gigan.site
# Root: /home/jon/bk/mysqldoc
--- 1.30/refman-4.1/news.xml 2005-06-25 03:41:10 +10:00
+++ 1.31/refman-4.1/news.xml 2005-06-29 00:34:51 +10:00
@@ -57,9 +57,10 @@
building and testing all packages takes some time.
</para>
-<!-- Please don't add a new highest-numbered version here without also -->
-
-<!-- updating Docs/include.texi! -->
+<!--
+ When adding a new News section, be sure to define an appropriate
+ entity reference in titles.ent and use this for the title text.
+-->
<section id="news-5-0-x">
@@ -207,47 +208,58 @@
<section id="news-5-0-9">
- <title id="title-news-5-0-9">&title-news-5-0-9;</title>
-
- <para>
- Functionality added or changed:
- </para>
-
- <itemizedlist>
-
- <listitem><para></para></listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem><para>
- Optimizer performed range check when comparing unsigned integers to
- negative constants, could cause errors. (Bug #11185)
- </para></listitem>
-
- <listitem><para>
- Wrong comparison method used in <literal>VIEW</literal> when
- relaxed date syntax used (i.e. <literal>2005.06.10</literal>). (Bug
- #11325)
- </para></listitem>
+ <title id="title-news-5-0-9">&title-news-5-0-9;</title>
+
+ <para>
+ Functionality added or changed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem><para></para></listitem>
+
+ </itemizedlist>
+
+ <para>
+ Bugs fixed:
+ </para>
- <listitem><para>
- The <literal>ENCRYPT()</literal> and
- <literal>SUBSTRING_INDEX()</literal> functions would cause errors
- when used with a <literal>VIEW</literal>. (Bug #7024)
- </para></listitem>
+ <itemizedlist>
+
+ <listitem>
+ <para>For <literal>MEMORY</literal> tables, it was possible for
+ for updates to be performed using outdated key statistics when
+ the updates involved only very small changes in a very few rows.
+ This resulted in the random failures of queries such as
+ <literal>UPDATE t SET col = col + 1 WHERE col_key = 2;</literal>
+ where the same query with no <literal>WHERE</literal> clause
+ would succeed. (Bug #10178)</para>
+ </listitem>
+
- <listitem><para>
- Clients would hang following some errors with stored procedures.
- (Bug #9503)
- </para></listitem>
+ <listitem><para>
+ Optimizer performed range check when comparing unsigned integers to
+ negative constants, could cause errors. (Bug #11185)
+ </para></listitem>
+
+ <listitem><para>
+ Wrong comparison method used in <literal>VIEW</literal> when
+ relaxed date syntax used (i.e. <literal>2005.06.10</literal>). (Bug
+ #11325)
+ </para></listitem>
+
+ <listitem><para>
+ The <literal>ENCRYPT()</literal> and
+ <literal>SUBSTRING_INDEX()</literal> functions would cause errors
+ when used with a <literal>VIEW</literal>. (Bug #7024)
+ </para></listitem>
+
+ <listitem><para>
+ Clients would hang following some errors with stored procedures.
+ (Bug #9503)
+ </para></listitem>
- </itemizedlist>
+ </itemizedlist>
</section>
@@ -420,6 +432,14 @@
Thanks!
-->
+ <listitem>
+ <para><literal>mysqld_safe</literal> would sometimes fail to
+ remove the pid file for the old <literal>mysql</literal> process
+ after a crash. As a result, the server would fail to start due to
+ a false <literal>A mysqld process already exists...</literal>
+ error. (Bug #11122)</para>
+ </listitem>
+
<listitem><para>
<literal>CAST( ... AS DECIMAL) didn't work for strings. (Bug
#11283)</literal>
@@ -4684,14 +4704,33 @@
Bugs fixed:
</para>
- <itemizedlist>
+ <itemizedlist>
<!-- NOTE: No need to start every item with "Fixed..."; sufficient to
- describe the issue that was fixed. Use past tense. -->
+ describe the issue that was fixed. Use past tense. -->
- <listitem><para>
- <literal>NULLIF()</literal> function could produce incorrect
- results if first argument is <literal>NULL</literal>. (Bug #11142)
+ <listitem>
+ <para><literal>mysqld_safe</literal> would sometimes fail to
+ remove the pid file for the old <literal>mysql</literal> process
+ after a crash. As a result, the server would fail to start due
+ to a false <literal>A mysqld process already exists...</literal>
+ error. (Bug #11122)</para>
+ </listitem>
+
+ <listitem>
+ <para>For <literal>MEMORY</literal> tables, it was possible for
+ for updates to be performed using outdated key statistics when
+ the updates involved only very small changes in a very few rows.
+ This resulted in the random failures of queries such as
+ <literal>UPDATE t SET col = col + 1 WHERE col_key = 2;</literal>
+ where the same query with no <literal>WHERE</literal> clause
+ would succeed. (Bug #10178)</para>
+ </listitem>
+
+ <listitem><para>
+ The <literal>NULLIF()</literal> function could produce incorrect
+ results if the first argument was <literal>NULL</literal>.
+ (Bug #11142)
</para></listitem>
<listitem><para>
--- 1.30/refman-5.0/news.xml 2005-06-25 03:41:10 +10:00
+++ 1.31/refman-5.0/news.xml 2005-06-29 00:34:51 +10:00
@@ -57,9 +57,10 @@
building and testing all packages takes some time.
</para>
-<!-- Please don't add a new highest-numbered version here without also -->
-
-<!-- updating Docs/include.texi! -->
+<!--
+ When adding a new News section, be sure to define an appropriate
+ entity reference in titles.ent and use this for the title text.
+-->
<section id="news-5-0-x">
@@ -207,47 +208,58 @@
<section id="news-5-0-9">
- <title id="title-news-5-0-9">&title-news-5-0-9;</title>
-
- <para>
- Functionality added or changed:
- </para>
-
- <itemizedlist>
-
- <listitem><para></para></listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem><para>
- Optimizer performed range check when comparing unsigned integers to
- negative constants, could cause errors. (Bug #11185)
- </para></listitem>
-
- <listitem><para>
- Wrong comparison method used in <literal>VIEW</literal> when
- relaxed date syntax used (i.e. <literal>2005.06.10</literal>). (Bug
- #11325)
- </para></listitem>
+ <title id="title-news-5-0-9">&title-news-5-0-9;</title>
+
+ <para>
+ Functionality added or changed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem><para></para></listitem>
+
+ </itemizedlist>
+
+ <para>
+ Bugs fixed:
+ </para>
- <listitem><para>
- The <literal>ENCRYPT()</literal> and
- <literal>SUBSTRING_INDEX()</literal> functions would cause errors
- when used with a <literal>VIEW</literal>. (Bug #7024)
- </para></listitem>
+ <itemizedlist>
+
+ <listitem>
+ <para>For <literal>MEMORY</literal> tables, it was possible for
+ for updates to be performed using outdated key statistics when
+ the updates involved only very small changes in a very few rows.
+ This resulted in the random failures of queries such as
+ <literal>UPDATE t SET col = col + 1 WHERE col_key = 2;</literal>
+ where the same query with no <literal>WHERE</literal> clause
+ would succeed. (Bug #10178)</para>
+ </listitem>
+
- <listitem><para>
- Clients would hang following some errors with stored procedures.
- (Bug #9503)
- </para></listitem>
+ <listitem><para>
+ Optimizer performed range check when comparing unsigned integers to
+ negative constants, could cause errors. (Bug #11185)
+ </para></listitem>
+
+ <listitem><para>
+ Wrong comparison method used in <literal>VIEW</literal> when
+ relaxed date syntax used (i.e. <literal>2005.06.10</literal>). (Bug
+ #11325)
+ </para></listitem>
+
+ <listitem><para>
+ The <literal>ENCRYPT()</literal> and
+ <literal>SUBSTRING_INDEX()</literal> functions would cause errors
+ when used with a <literal>VIEW</literal>. (Bug #7024)
+ </para></listitem>
+
+ <listitem><para>
+ Clients would hang following some errors with stored procedures.
+ (Bug #9503)
+ </para></listitem>
- </itemizedlist>
+ </itemizedlist>
</section>
@@ -420,6 +432,14 @@
Thanks!
-->
+ <listitem>
+ <para><literal>mysqld_safe</literal> would sometimes fail to
+ remove the pid file for the old <literal>mysql</literal> process
+ after a crash. As a result, the server would fail to start due to
+ a false <literal>A mysqld process already exists...</literal>
+ error. (Bug #11122)</para>
+ </listitem>
+
<listitem><para>
<literal>CAST( ... AS DECIMAL) didn't work for strings. (Bug
#11283)</literal>
@@ -4684,14 +4704,33 @@
Bugs fixed:
</para>
- <itemizedlist>
+ <itemizedlist>
<!-- NOTE: No need to start every item with "Fixed..."; sufficient to
- describe the issue that was fixed. Use past tense. -->
+ describe the issue that was fixed. Use past tense. -->
- <listitem><para>
- <literal>NULLIF()</literal> function could produce incorrect
- results if first argument is <literal>NULL</literal>. (Bug #11142)
+ <listitem>
+ <para><literal>mysqld_safe</literal> would sometimes fail to
+ remove the pid file for the old <literal>mysql</literal> process
+ after a crash. As a result, the server would fail to start due
+ to a false <literal>A mysqld process already exists...</literal>
+ error. (Bug #11122)</para>
+ </listitem>
+
+ <listitem>
+ <para>For <literal>MEMORY</literal> tables, it was possible for
+ for updates to be performed using outdated key statistics when
+ the updates involved only very small changes in a very few rows.
+ This resulted in the random failures of queries such as
+ <literal>UPDATE t SET col = col + 1 WHERE col_key = 2;</literal>
+ where the same query with no <literal>WHERE</literal> clause
+ would succeed. (Bug #10178)</para>
+ </listitem>
+
+ <listitem><para>
+ The <literal>NULLIF()</literal> function could produce incorrect
+ results if the first argument was <literal>NULL</literal>.
+ (Bug #11142)
</para></listitem>
<listitem><para>
--- 1.35/refman/news.xml 2005-06-25 03:41:11 +10:00
+++ 1.36/refman/news.xml 2005-06-29 00:34:51 +10:00
@@ -57,9 +57,10 @@
building and testing all packages takes some time.
</para>
-<!-- Please don't add a new highest-numbered version here without also -->
-
-<!-- updating Docs/include.texi! -->
+<!--
+ When adding a new News section, be sure to define an appropriate
+ entity reference in titles.ent and use this for the title text.
+-->
<section id="news-5-0-x">
@@ -207,47 +208,58 @@
<section id="news-5-0-9">
- <title id="title-news-5-0-9">&title-news-5-0-9;</title>
-
- <para>
- Functionality added or changed:
- </para>
-
- <itemizedlist>
-
- <listitem><para></para></listitem>
-
- </itemizedlist>
-
- <para>
- Bugs fixed:
- </para>
-
- <itemizedlist>
-
- <listitem><para>
- Optimizer performed range check when comparing unsigned integers to
- negative constants, could cause errors. (Bug #11185)
- </para></listitem>
-
- <listitem><para>
- Wrong comparison method used in <literal>VIEW</literal> when
- relaxed date syntax used (i.e. <literal>2005.06.10</literal>). (Bug
- #11325)
- </para></listitem>
+ <title id="title-news-5-0-9">&title-news-5-0-9;</title>
+
+ <para>
+ Functionality added or changed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem><para></para></listitem>
+
+ </itemizedlist>
+
+ <para>
+ Bugs fixed:
+ </para>
- <listitem><para>
- The <literal>ENCRYPT()</literal> and
- <literal>SUBSTRING_INDEX()</literal> functions would cause errors
- when used with a <literal>VIEW</literal>. (Bug #7024)
- </para></listitem>
+ <itemizedlist>
+
+ <listitem>
+ <para>For <literal>MEMORY</literal> tables, it was possible for
+ for updates to be performed using outdated key statistics when
+ the updates involved only very small changes in a very few rows.
+ This resulted in the random failures of queries such as
+ <literal>UPDATE t SET col = col + 1 WHERE col_key = 2;</literal>
+ where the same query with no <literal>WHERE</literal> clause
+ would succeed. (Bug #10178)</para>
+ </listitem>
+
- <listitem><para>
- Clients would hang following some errors with stored procedures.
- (Bug #9503)
- </para></listitem>
+ <listitem><para>
+ Optimizer performed range check when comparing unsigned integers to
+ negative constants, could cause errors. (Bug #11185)
+ </para></listitem>
+
+ <listitem><para>
+ Wrong comparison method used in <literal>VIEW</literal> when
+ relaxed date syntax used (i.e. <literal>2005.06.10</literal>). (Bug
+ #11325)
+ </para></listitem>
+
+ <listitem><para>
+ The <literal>ENCRYPT()</literal> and
+ <literal>SUBSTRING_INDEX()</literal> functions would cause errors
+ when used with a <literal>VIEW</literal>. (Bug #7024)
+ </para></listitem>
+
+ <listitem><para>
+ Clients would hang following some errors with stored procedures.
+ (Bug #9503)
+ </para></listitem>
- </itemizedlist>
+ </itemizedlist>
</section>
@@ -420,6 +432,14 @@
Thanks!
-->
+ <listitem>
+ <para><literal>mysqld_safe</literal> would sometimes fail to
+ remove the pid file for the old <literal>mysql</literal> process
+ after a crash. As a result, the server would fail to start due to
+ a false <literal>A mysqld process already exists...</literal>
+ error. (Bug #11122)</para>
+ </listitem>
+
<listitem><para>
<literal>CAST( ... AS DECIMAL) didn't work for strings. (Bug
#11283)</literal>
@@ -4666,14 +4686,33 @@
Bugs fixed:
</para>
- <itemizedlist>
+ <itemizedlist>
<!-- NOTE: No need to start every item with "Fixed..."; sufficient to
- describe the issue that was fixed. Use past tense. -->
+ describe the issue that was fixed. Use past tense. -->
- <listitem><para>
- <literal>NULLIF()</literal> function could produce incorrect
- results if first argument is <literal>NULL</literal>. (Bug #11142)
+ <listitem>
+ <para><literal>mysqld_safe</literal> would sometimes fail to
+ remove the pid file for the old <literal>mysql</literal> process
+ after a crash. As a result, the server would fail to start due
+ to a false <literal>A mysqld process already exists...</literal>
+ error. (Bug #11122)</para>
+ </listitem>
+
+ <listitem>
+ <para>For <literal>MEMORY</literal> tables, it was possible for
+ for updates to be performed using outdated key statistics when
+ the updates involved only very small changes in a very few rows.
+ This resulted in the random failures of queries such as
+ <literal>UPDATE t SET col = col + 1 WHERE col_key = 2;</literal>
+ where the same query with no <literal>WHERE</literal> clause
+ would succeed. (Bug #10178)</para>
+ </listitem>
+
+ <listitem><para>
+ The <literal>NULLIF()</literal> function could produce incorrect
+ results if the first argument was <literal>NULL</literal>.
+ (Bug #11142)
</para></listitem>
<listitem><para>
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (jon:1.2896) | jon | 28 Jun |
