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.3001 05/07/12 14:16:04 paul@stripped +3 -0
Format.
refman/news.xml
1.56 05/07/12 14:16:04 paul@stripped +127 -134
Format.
refman-5.0/news.xml
1.51 05/07/12 14:16:03 paul@stripped +79 -91
Format.
refman-4.1/news.xml
1.42 05/07/12 14:16:03 paul@stripped +51 -57
Format.
# 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.41/refman-4.1/news.xml 2005-07-12 02:17:51 -05:00
+++ 1.42/refman-4.1/news.xml 2005-07-12 14:16:03 -05:00
@@ -255,39 +255,38 @@
<!-- NOTE: No need to start every item with "Fixed..."; sufficient to
describe the issue that was fixed. Use past tense. -->
-
- <listitem><para>
- When used in joins, <literal>SUBSTRING()</literal> failed to
- truncate to zero those string values that could not be
- converted to numbers. (Bug #10124)
- </para></listitem>
+
+ <listitem><para>
+ When used in joins, <literal>SUBSTRING()</literal> failed to
+ truncate to zero those string values that could not be converted to
+ numbers. (Bug #10124)
+ </para></listitem>
<listitem><para>
Error when performing <literal>GROUP BY</literal> on calculated
values of a single row table. (Bug #11414)
</para></listitem>
-
- <listitem><para>
- <literal>mysqldump --xml</literal> did not format
- <literal>NULL</literal> column values correctly. (Bug #9657)
- </para></listitem>
-
- <listitem><para>
- <literal>SHOW WARNINGS</literal> did not properly display
- warnings generated by executing a cached query. (Bug #9414)
- </para></listitem>
<listitem><para>
- Temporary tables were created in the data directory instead of
- <literal>tmpdir</literal>. (Bug #11440)
- </para></listitem>
-
+ <literal>mysqldump --xml</literal> did not format
+ <literal>NULL</literal> column values correctly. (Bug #9657)
+ </para></listitem>
+
<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>
+ <literal>SHOW WARNINGS</literal> did not properly display warnings
+ generated by executing a cached query. (Bug #9414)
+ </para></listitem>
+
+ <listitem><para>
+ Temporary tables were created in the data directory instead of
+ <literal>tmpdir</literal>. (Bug #11440)
+ </para></listitem>
+
+ <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>
Incorrect results when searching using <literal>IN()</literal>
@@ -884,14 +883,14 @@
it would run using the privileges of the account it was invoked
from, even if that was <literal>root</literal>. (Bug #9833)
</para></listitem>
-
- <listitem><para>
- An error in the implementation of the <literal>MyISAM</literal>
- compression algorithm caused <literal>myisampack</literal> to
- fail with very large sets of data (total size of all the
- records in a single column needed to be >= 3 GB in order to
- trigger this issue). (Bug #8321)
- </para></listitem>
+
+ <listitem><para>
+ An error in the implementation of the <literal>MyISAM</literal>
+ compression algorithm caused <literal>myisampack</literal> to fail
+ with very large sets of data (total size of all the records in a
+ single column needed to be >= 3 GB in order to trigger this
+ issue). (Bug #8321)
+ </para></listitem>
<listitem><para>
When <literal>SELECT <replaceable>constant</replaceable></literal>
@@ -6847,14 +6846,14 @@
</para>
<itemizedlist>
-
- <listitem><para>
- An error in the implementation of the <literal>MyISAM</literal>
- compression algorithm caused <literal>myisampack</literal> to
- fail with very large sets of data (total size of all the
- records in a single column needed to be >= 3 GB in order to
- trigger this issue). (Bug #8321)
- </para></listitem>
+
+ <listitem><para>
+ An error in the implementation of the <literal>MyISAM</literal>
+ compression algorithm caused <literal>myisampack</literal> to fail
+ with very large sets of data (total size of all the records in a
+ single column needed to be >= 3 GB in order to trigger this
+ issue). (Bug #8321)
+ </para></listitem>
<listitem><para>
A problem with the <filename>my_global.h</filename> file caused
@@ -28579,22 +28578,17 @@
</para>
<itemizedlist>
-
- <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>
+ <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>
Error when performing <literal>GROUP BY</literal> on calculated
--- 1.50/refman-5.0/news.xml 2005-07-12 09:37:39 -05:00
+++ 1.51/refman-5.0/news.xml 2005-07-12 14:16:03 -05:00
@@ -219,39 +219,35 @@
</para>
<itemizedlist>
-
- <listitem><para>
- Execution of a prepared statement that invoked a non-existent
- or dropped stored routine would crash the server. (Bug #11834)
- </para></listitem>
-
- <listitem>
- <para>
- Executing a statement that invoked a trigger would cause
- problems unless a <literal>LOCK TABLES</literal> was first
- issued for any tables accessed by the trigger.
- <emphasis role="bold">Note</emphasis>: The exact nature of the
- problem depended upon the MySQL 5.0 release being used: prior
- to 5.0.3, this resulted in a crash; from 5.0.3 to 5.0.7, MySQL
- would issue a warning; in 5.0.9, the server would issue an
- error. (Bug #8406)
- </para>
-
- <para>
- The same issue caused <literal>LOCK TABLES</literal> to
- fail following <literal>UNLOCK TABLES</literal> if triggers
- were involved. (Bug #9581)
- </para>
- </listitem>
-
- <listitem>
- <para>
- It is no longer necessary to issue an explicit <literal>LOCK
- TABLES</literal> for any tables accessed by a trigger prior to
- executing any statements that might invoke the trigger. (Bug
- #9581, Bug #8406)
- </para>
- </listitem>
+
+ <listitem><para>
+ Execution of a prepared statement that invoked a non-existent or
+ dropped stored routine would crash the server. (Bug #11834)
+ </para></listitem>
+
+ <listitem><para>
+ Executing a statement that invoked a trigger would cause problems
+ unless a <literal>LOCK TABLES</literal> was first issued for any
+ tables accessed by the trigger.
+ <emphasis role="bold">Note</emphasis>: The exact nature of the
+ problem depended upon the MySQL 5.0 release being used: prior to
+ 5.0.3, this resulted in a crash; from 5.0.3 to 5.0.7, MySQL would
+ issue a warning; in 5.0.9, the server would issue an error. (Bug
+ #8406)
+ </para>
+
+ <para>
+ The same issue caused <literal>LOCK TABLES</literal> to fail
+ following <literal>UNLOCK TABLES</literal> if triggers were
+ involved. (Bug #9581)
+ </para></listitem>
+
+ <listitem><para>
+ It is no longer necessary to issue an explicit <literal>LOCK
+ TABLES</literal> for any tables accessed by a trigger prior to
+ executing any statements that might invoke the trigger. (Bug #9581,
+ Bug #8406)
+ </para></listitem>
</itemizedlist>
@@ -328,56 +324,48 @@
</para>
<itemizedlist>
-
- <listitem><para>
- When used in joins, <literal>SUBSTRING()</literal> failed to
- truncate to zero any string values that could not be converted
- to numbers. (Bug #10124)
- </para></listitem>
-
- <listitem><para>
- <literal>mysqldump --xml</literal> did not format
- <literal>NULL</literal> column values correctly. (Bug #9657)
- </para></listitem>
-
- <listitem><para>
- There was a compression algorithm issue with
- <literal>myisampack</literal> for very large datasets (where
- the total size of of all records in a single column was on the
- order of 3 GB or more) on 64-bit platforms. (A fix for other
- platforms was made in MySQL 5.0.6.) (Bug #8321)
- </para></listitem>
-
- <listitem><para>
- Temporary tables were created in the data directory instead of
- <literal>tmpdir</literal>. (Bug #11440)
- </para></listitem>
-
- <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>
+ When used in joins, <literal>SUBSTRING()</literal> failed to
+ truncate to zero any string values that could not be converted to
+ numbers. (Bug #10124)
+ </para></listitem>
+
+ <listitem><para>
+ <literal>mysqldump --xml</literal> did not format
+ <literal>NULL</literal> column values correctly. (Bug #9657)
+ </para></listitem>
+
+ <listitem><para>
+ There was a compression algorithm issue with
+ <literal>myisampack</literal> for very large datasets (where the
+ total size of of all records in a single column was on the order of
+ 3 GB or more) on 64-bit platforms. (A fix for other platforms was
+ made in MySQL 5.0.6.) (Bug #8321)
+ </para></listitem>
+
+ <listitem><para>
+ Temporary tables were created in the data directory instead of
+ <literal>tmpdir</literal>. (Bug #11440)
+ </para></listitem>
+
+ <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
@@ -1608,14 +1596,14 @@
</para>
<itemizedlist>
-
- <listitem><para>
- An error in the implementation of the <literal>MyISAM</literal>
- compression algorithm caused <literal>myisampack</literal> to
- fail with very large sets of data (total size of all the
- records in a single column needed to be >= 3 GB in order to
- trigger this issue). (Bug #8321)
- </para></listitem>
+
+ <listitem><para>
+ An error in the implementation of the <literal>MyISAM</literal>
+ compression algorithm caused <literal>myisampack</literal> to fail
+ with very large sets of data (total size of all the records in a
+ single column needed to be >= 3 GB in order to trigger this
+ issue). (Bug #8321)
+ </para></listitem>
<listitem><para>
Statements that create and use stored routines were not being
--- 1.55/refman/news.xml 2005-07-12 09:37:09 -05:00
+++ 1.56/refman/news.xml 2005-07-12 14:16:04 -05:00
@@ -216,14 +216,12 @@
<itemizedlist>
- <listitem>
- <para>
- It is no longer necessary to issue an explicit <literal>LOCK
- TABLES</literal> for any tables accessed by a trigger prior to
- executing any statements that might invoke the trigger. (Bug
- #9581, Bug #8406)
- </para>
- </listitem>
+ <listitem><para>
+ It is no longer necessary to issue an explicit <literal>LOCK
+ TABLES</literal> for any tables accessed by a trigger prior to
+ executing any statements that might invoke the trigger. (Bug #9581,
+ Bug #8406)
+ </para></listitem>
</itemizedlist>
@@ -232,30 +230,28 @@
</para>
<itemizedlist>
-
- <listitem><para>
- Execution of a prepared statement that invoked a non-existent
- or dropped stored routine would crash the server. (Bug #11834)
- </para></listitem>
-
- <listitem>
- <para>
- Executing a statement that invoked a trigger would cause
- problems unless a <literal>LOCK TABLES</literal> was first
- issued for any tables accessed by the trigger.
- <emphasis role="bold">Note</emphasis>: The exact nature of the
- problem depended upon the MySQL 5.0 release being used: prior
- to 5.0.3, this resulted in a crash; from 5.0.3 to 5.0.7, MySQL
- would issue a warning; in 5.0.9, the server would issue an
- error. (Bug #8406)
- </para>
-
- <para>
- The same issue caused <literal>LOCK TABLES</literal> to
- fail following <literal>UNLOCK TABLES</literal> if triggers
- were involved. (Bug #9581)
- </para>
- </listitem>
+
+ <listitem><para>
+ Execution of a prepared statement that invoked a non-existent or
+ dropped stored routine would crash the server. (Bug #11834)
+ </para></listitem>
+
+ <listitem><para>
+ Executing a statement that invoked a trigger would cause problems
+ unless a <literal>LOCK TABLES</literal> was first issued for any
+ tables accessed by the trigger.
+ <emphasis role="bold">Note</emphasis>: The exact nature of the
+ problem depended upon the MySQL 5.0 release being used: prior to
+ 5.0.3, this resulted in a crash; from 5.0.3 to 5.0.7, MySQL would
+ issue a warning; in 5.0.9, the server would issue an error. (Bug
+ #8406)
+ </para>
+
+ <para>
+ The same issue caused <literal>LOCK TABLES</literal> to fail
+ following <literal>UNLOCK TABLES</literal> if triggers were
+ involved. (Bug #9581)
+ </para></listitem>
<listitem><para>
In a shared Windows environment, MySQL could not find its
@@ -324,50 +320,48 @@
</para>
<itemizedlist>
-
- <listitem><para>
- When used in joins, <literal>SUBSTRING()</literal> failed to
- truncate to zero any string values that could not be converted
- to numbers. (Bug #10124)
- </para></listitem>
-
- <listitem><para>
- <literal>mysqldump --xml</literal> did not format
- <literal>NULL</literal> column values correctly. (Bug #9657)
- </para></listitem>
-
- <listitem><para>
- There was a compression algorithm issue with
- <literal>myisampack</literal> for very large datasets (where
- the total size of of all records in a single column was on the
- order of 3 GB or more) on 64-bit platforms. (A fix for other
- platforms was made in MySQL 5.0.6.) (Bug #8321)
- </para></listitem>
-
- <listitem><para>
- Temporary tables were created in the data directory instead of
- <literal>tmpdir</literal>. (Bug #11440)
- </para></listitem>
-
- <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>
+ When used in joins, <literal>SUBSTRING()</literal> failed to
+ truncate to zero any string values that could not be converted to
+ numbers. (Bug #10124)
+ </para></listitem>
+
+ <listitem><para>
+ <literal>mysqldump --xml</literal> did not format
+ <literal>NULL</literal> column values correctly. (Bug #9657)
+ </para></listitem>
+
+ <listitem><para>
+ There was a compression algorithm issue with
+ <literal>myisampack</literal> for very large datasets (where the
+ total size of of all records in a single column was on the order of
+ 3 GB or more) on 64-bit platforms. (A fix for other platforms was
+ made in MySQL 5.0.6.) (Bug #8321)
+ </para></listitem>
+
+ <listitem><para>
+ Temporary tables were created in the data directory instead of
+ <literal>tmpdir</literal>. (Bug #11440)
+ </para></listitem>
+
+ <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
@@ -478,7 +472,7 @@
sentence describing the bugfix, like this:
This sentence describes the fix. (Bug #nnnn)
--->
+-->
<para>
<emphasis role="bold">Note</emphasis>: Starting with version 5.0.8,
@@ -1598,14 +1592,14 @@
</para>
<itemizedlist>
-
- <listitem><para>
- An error in the implementation of the <literal>MyISAM</literal>
- compression algorithm caused <literal>myisampack</literal> to
- fail with very large sets of data (total size of all the
- records in a single column needed to be >= 3 GB in order to
- trigger this issue). (Bug #8321)
- </para></listitem>
+
+ <listitem><para>
+ An error in the implementation of the <literal>MyISAM</literal>
+ compression algorithm caused <literal>myisampack</literal> to fail
+ with very large sets of data (total size of all the records in a
+ single column needed to be >= 3 GB in order to trigger this
+ issue). (Bug #8321)
+ </para></listitem>
<listitem><para>
Statements that create and use stored routines were not being
@@ -4947,44 +4941,43 @@
describe the issue that was fixed. Use past tense. -->
<itemizedlist>
-
- <listitem><para>
- When used in joins, <literal>SUBSTRING()</literal> failed to
- truncate to zero those string values that could not be
- converted to numbers. (Bug #10124)
- </para></listitem>
+
+ <listitem><para>
+ When used in joins, <literal>SUBSTRING()</literal> failed to
+ truncate to zero those string values that could not be converted to
+ numbers. (Bug #10124)
+ </para></listitem>
<listitem><para>
Error when performing <literal>GROUP BY</literal> on calculated
values of a single row table. (Bug #11414)
</para></listitem>
-
- <listitem><para>
- <literal>mysqldump --xml</literal> did not format
- <literal>NULL</literal> column values correctly. (Bug #9657)
- </para></listitem>
-
- <listitem><para>
- <literal>SHOW WARNINGS</literal> did not properly display
- warnings generated by executing a cached query. (Bug #9414)
- </para></listitem>
<listitem><para>
- Temporary tables were created in the data directory instead of
- <literal>tmpdir</literal>. (Bug #11440)
- </para></listitem>
-
+ <literal>mysqldump --xml</literal> did not format
+ <literal>NULL</literal> column values correctly. (Bug #9657)
+ </para></listitem>
+
<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>
+ <literal>SHOW WARNINGS</literal> did not properly display warnings
+ generated by executing a cached query. (Bug #9414)
+ </para></listitem>
<listitem><para>
- MySQL would not compile correctly on QNX due to missing
- <literal>rint()</literal> function. (Bug #11544)
- </para></listitem>
+ Temporary tables were created in the data directory instead of
+ <literal>tmpdir</literal>. (Bug #11440)
+ </para></listitem>
+
+ <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>
@@ -5528,14 +5521,14 @@
it would run using the privileges of the account it was invoked
from, even if that was <literal>root</literal>. (Bug #9833)
</para></listitem>
-
- <listitem><para>
- An error in the implementation of the <literal>MyISAM</literal>
- compression algorithm caused <literal>myisampack</literal> to
- fail with very large sets of data (total size of all the
- records in a single column needed to be >= 3 GB in order to
- trigger this issue). (Bug #8321)
- </para></listitem>
+
+ <listitem><para>
+ An error in the implementation of the <literal>MyISAM</literal>
+ compression algorithm caused <literal>myisampack</literal> to fail
+ with very large sets of data (total size of all the records in a
+ single column needed to be >= 3 GB in order to trigger this
+ issue). (Bug #8321)
+ </para></listitem>
<listitem><para>
When <literal>SELECT <replaceable>constant</replaceable></literal>
@@ -11491,14 +11484,14 @@
</para>
<itemizedlist>
-
- <listitem><para>
- An error in the implementation of the <literal>MyISAM</literal>
- compression algorithm caused <literal>myisampack</literal> to
- fail with very large sets of data (total size of all the
- records in a single column needed to be >= 3 GB in order to
- trigger this issue). (Bug #8321)
- </para></listitem>
+
+ <listitem><para>
+ An error in the implementation of the <literal>MyISAM</literal>
+ compression algorithm caused <literal>myisampack</literal> to fail
+ with very large sets of data (total size of all the records in a
+ single column needed to be >= 3 GB in order to trigger this
+ issue). (Bug #8321)
+ </para></listitem>
<listitem><para>
A problem with the <filename>my_global.h</filename> file caused
@@ -33005,11 +32998,11 @@
</para>
<itemizedlist>
-
- <listitem><para>
- The server would hang on successive calls to an <literal>INSERT
- ... ON DUPLICATE KEY UPDATE</literal> query. (Bug #9725)
- </para></listitem>
+
+ <listitem><para>
+ The server would hang on successive calls to an <literal>INSERT ...
+ ON DUPLICATE KEY UPDATE</literal> query. (Bug #9725)
+ </para></listitem>
<listitem><para>
(Bug #10193) Invalid DataDir in config causes ndbd segfault
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (paul:1.3001) | paul | 12 Jul |
