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.3309 05/08/17 14:33:09 paul@stripped +2 -0
news-5.0.xml:
Document bugfix. (Bug #12569)
news-5.0.xml, news-4.1.xml:
Document bugfix. (Bug #6581)
news-5.0.xml:
Document bugfix. (Bug #12301)
Document bugfix. (Bug #12518)
news-5.0.xml, news-4.1.xml:
Document bugfix. (Bug #10780)
refman-common/news-5.0.xml
1.72 05/08/17 14:30:54 paul@stripped +8 -0
Document bugfix. (Bug #12569)
refman-common/news-5.0.xml
1.71 05/08/17 14:27:59 paul@stripped +10 -0
Document bugfix. (Bug #6581)
refman-common/news-4.1.xml
1.44 05/08/17 14:26:43 paul@stripped +39 -0
Document bugfix. (Bug #6581)
refman-common/news-5.0.xml
1.70 05/08/17 14:19:14 paul@stripped +9 -0
Document bugfix. (Bug #12301)
refman-common/news-5.0.xml
1.69 05/08/17 14:16:53 paul@stripped +10 -0
Document bugfix. (Bug #12518)
refman-common/news-5.0.xml
1.68 05/08/17 14:11:28 paul@stripped +9 -0
Document bugfix. (Bug #10780)
refman-common/news-4.1.xml
1.43 05/08/17 14:11:19 paul@stripped +9 -0
Document bugfix. (Bug #10780)
# 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.42/refman-common/news-4.1.xml 2005-08-17 13:19:38 -05:00
+++ 1.44/refman-common/news-4.1.xml 2005-08-17 14:26:43 -05:00
@@ -151,6 +151,45 @@
for each individual 4.1.x release.
</para>
+ <section id="news-4-1-15">
+
+ <title id='title-news-4-1-15'>&title-news-4-1-15;</title>
+
+<!--
+ NOTE: References to bug numbers should be written after the sentence
+ describing the bugfix, like this:
+ This sentence describes the fix. (Bug #nnnn)
+-->
+
+ <para>
+ Functionality added or changed:
+ </para>
+
+<!-- REPLACE WITH <itemizedlist> WHEN THERE ARE ITEMS FOR THIS LIST -->
+
+ <para>
+ Bugs fixed:
+ </para>
+
+<!-- NOTE: No need to start every item with "Fixed..."; sufficient to
+ describe the issue that was fixed. Use past tense. -->
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ On Windows when the
+ <option>--innodb_buffer_pool_awe_mem_mb</option> option has
+ been given, the server detects whether AWE support is
+ available and has been compiled into the server, and displays
+ an appropriate error message if not. (Bug #6581)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
<section id="news-4-1-14">
<title id='title-news-4-1-14'>&title-news-4-1-14;</title>
@@ -247,6 +286,15 @@
describe the issue that was fixed. Use past tense. -->
<itemizedlist>
+
+ <listitem>
+ <para>
+ Slave I/O threads were considered to be in the running state
+ when launched (rather than after successfully connecting to
+ the master server), resulting in incorrect <literal>SHOW SLAVE
+ STATUS</literal> output. (Bug #10780)
+ </para>
+ </listitem>
<listitem>
<para>
--- 1.67/refman-common/news-5.0.xml 2005-08-17 13:24:10 -05:00
+++ 1.72/refman-common/news-5.0.xml 2005-08-17 14:30:54 -05:00
@@ -248,6 +248,52 @@
<listitem>
<para>
+ A server crash could result from an update of a view defined
+ as a join, even though the update only updated a single table.
+ (Bug #12569)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On Windows when the
+ <option>--innodb_buffer_pool_awe_mem_mb</option> option has
+ been given, the server detects whether AWE support is
+ available and has been compiled into the server, and displays
+ an appropriate error message if not. (Bug #6581)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>NUMERIC_SCALE</literal> column of the
+ <literal>INFORMATION_SCHEMA.COLUMNS</literal> table should be
+ returned as <literal>0</literal> for integer columns. It was
+ being returned as <literal>NULL</literal>. (Bug #12301)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>COLUMN_DEFAULT</literal> column of the
+ <literal>INFORMATION_SCHEMA.COLUMNS</literal> table should be
+ returned as <literal>NULL</literal> if a column has no default
+ value. An empty string was being returned if the column was
+ defined as <literal>NOT NULL</literal>. (Bug #12518)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Slave I/O threads were considered to be in the running state
+ when launched (rather than after successfully connecting to
+ the master server), resulting in incorrect <literal>SHOW SLAVE
+ STATUS</literal> output. (Bug #10780)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Column names in subqueries must be unique, but were not being
checked for uniqueness. (Bug #11796)
</para>
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (paul:1.3309) | paul | 17 Aug |
