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.2969 05/07/09 05:25:42 jon@stripped +3 -0
Merge bk://mysqldoc@stripped
into gigan.homedns.org:/home/jon/bk/mysqldoc
refman-5.0/news.xml
1.44 05/07/09 05:09:00 jon@stripped +0 -0
Auto merged
refman-4.1/news.xml
1.38 05/07/09 05:08:59 jon@stripped +0 -0
Auto merged
refman/news.xml
1.49 05/07/09 05:08:58 jon@stripped +0 -0
Auto merged
# 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.
# Root: /home/jon/bk/mysqldoc/RESYNC
--- 1.37/refman-4.1/news.xml 2005-07-09 01:50:43 +10:00
+++ 1.38/refman-4.1/news.xml 2005-07-09 05:08:59 +10:00
@@ -274,6 +274,22 @@
<!-- NOTE: No need to start every item with "Fixed..."; sufficient to
describe the issue that was fixed. Use past tense. -->
+ <listitem>
+ <para>
+ <literal>LOAD DATA ... REPLACE INTO ...</literal> on a
+ replication slave failed for an <literal>InnoDB</literal> table
+ having a unique index in addition to the primary key.
+ (Bug #11401)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ MySQL would not compile correctly on QNX due to missing
+ <literal>rint()</literal> function. (Bug #11544)
+ </para>
+ </listitem>
+
<listitem><para>
Incorrect results when searching using <literal>IN()</literal>
where search items include <literal>NULL</literal> and
--- 1.43/refman-5.0/news.xml 2005-07-09 01:50:43 +10:00
+++ 1.44/refman-5.0/news.xml 2005-07-09 05:09:00 +10:00
@@ -168,36 +168,20 @@
<colspec colwidth="65*"/>
<tbody>
<row>
- <entry>
- <emphasis role="bold">max_length</emphasis>
- </entry>
- <entry>
- <emphasis role="bold">Column type</emphasis>
- </entry>
+ <entry><emphasis role="bold">max_length</emphasis></entry>
+ <entry><emphasis role="bold">Column type</emphasis></entry>
</row>
<row>
- <entry>
- = 0
- </entry>
- <entry>
- <literal>CHAR(0)</literal>
- </entry>
+ <entry>= 0</entry>
+ <entry><literal>CHAR(0)</literal></entry>
</row>
<row>
- <entry>
- < 512
- </entry>
- <entry>
- <literal>VARCHAR(max_length)</literal>
- </entry>
+ <entry>< 512</entry>
+ <entry><literal>VARCHAR(max_length)</literal></entry>
</row>
<row>
- <entry>
- >= 512
- </entry>
- <entry>
- <literal>TEXT</literal>
- </entry>
+ <entry>>= 512</entry>
+ <entry><literal>TEXT</literal></entry>
</row>
</tbody>
</tgroup>
@@ -263,7 +247,8 @@
<listitem><para>
Recursion in stored routines is now disabled because it was
crashing the server. We plan to modify stored routines to allow
- this to operate safely in a future release. (Bug #11394)
+ this to operate safely in a future release. (Bug #11394,
+ Bug #11600)
</para></listitem>
<listitem><para>
@@ -279,6 +264,32 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ MySQL would not compile correctly on QNX due to missing
+ <literal>rint()</literal> function. (Bug #11544)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A <literal>SELECT DISTINCT
+ <replaceable>col_name</replaceable></literal> would work
+ correctly with a <literal>MyISAM</literal> table only when
+ there was an index on <replaceable>col_name</replaceable>.
+ (Bug #11484)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The server would lose table-level <literal>CREATE
+ VIEW</literal> and <literal>SHOW VIEW</literal> privileges
+ following a <literal>FLUSH PRIVILEGES</literal> or server
+ restart. (Bug #9795)
+ </para>
+ </listitem>
<listitem><para>
In strict mode, an <literal>INSERT</literal> into a view that did
--- 1.48/refman/news.xml 2005-07-09 01:50:44 +10:00
+++ 1.49/refman/news.xml 2005-07-09 05:08:58 +10:00
@@ -259,7 +259,8 @@
<listitem><para>
Recursion in stored routines is now disabled because it was
crashing the server. We plan to modify stored routines to allow
- this to operate safely in a future release. (Bug #11394)
+ this to operate safely in a future release. (Bug #11394,
+ Bug #11600)
</para></listitem>
<listitem><para>
@@ -275,6 +276,32 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ MySQL would not compile correctly on QNX due to missing
+ <literal>rint()</literal> function. (Bug #11544)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A <literal>SELECT DISTINCT
+ <replaceable>col_name</replaceable></literal> would work
+ correctly with a <literal>MyISAM</literal> table only when
+ there was an index on <replaceable>col_name</replaceable>.
+ (Bug #11484)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The server would lose table-level <literal>CREATE
+ VIEW</literal> and <literal>SHOW VIEW</literal> privileges
+ following a <literal>FLUSH PRIVILEGES</literal> or server
+ restart. (Bug #9795)
+ </para>
+ </listitem>
<listitem><para>
In strict mode, an <literal>INSERT</literal> into a view that did
@@ -4846,6 +4873,22 @@
<!-- NOTE: No need to start every item with "Fixed..."; sufficient to
describe the issue that was fixed. Use past tense. -->
+
+ <listitem>
+ <para>
+ <literal>LOAD DATA ... REPLACE INTO ...</literal> on a
+ replication slave failed for an <literal>InnoDB</literal> table
+ having a unique index in addition to the primary key.
+ (Bug #11401)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ MySQL would not compile correctly on QNX due to missing
+ <literal>rint()</literal> function. (Bug #11544)
+ </para>
+ </listitem>
<listitem><para>
Incorrect results when searching using <literal>IN()</literal>
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (jon:1.2969) | jon | 11 Jul |
