Author: paul
Date: 2005-10-18 21:38:21 +0200 (Tue, 18 Oct 2005)
New Revision: 80
Log:
r2851@frost: paul | 2005-10-18 14:37:54 -0500
Small changelog revisions.
Modified:
trunk/
trunk/refman-common/news-5.0.xml
trunk/xsl.d/expand-links.xsl
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:2801
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:2851
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2005-10-18 17:22:15 UTC (rev 79)
+++ trunk/refman-common/news-5.0.xml 2005-10-18 19:38:21 UTC (rev 80)
@@ -127,7 +127,7 @@
When using a constant string or a function that generates a
string result in <literal>CREATE ... SELECT</literal>, MySQL
creates the result field based on the maximum length of the
- string or expression:
+ string or expression:
</para>
<informaltable>
@@ -161,8 +161,8 @@
<para>
For a full list of changes, please refer to the changelog sections
for each individual 5.0.x release.
- </para>
-
+ </para>
+
<section id="news-5-0-15">
<title id="title-news-5-0-15">&title-news-5-0-15;</title>
@@ -178,13 +178,13 @@
When declaring a local variable (or parameter) named
<literal>password</literal> or <literal>name</literal>, and
setting it with <literal>SET</literal>, e.g. <literal>SET
- password = ''</literal>, the new error message: <literal>ERROR 42000:
- Variable 'nnn' must be quoted with `...`, or renamed</literal>
- is returned (where 'nnn' is 'password' or 'names'). This means
- there is a syntax conflict with special sentences like
- <literal>SET PASSWORD = PASSWORD(...)</literal> (for setting a
- user's password) and <literal>set names default</literal> (for
- setting charset and collation).
+ password = ''</literal>, the new error message: <literal>ERROR
+ 42000: Variable 'nnn' must be quoted with `...`, or
+ renamed</literal> is returned (where 'nnn' is 'password' or
+ 'names'). This means there is a syntax conflict with special
+ sentences like <literal>SET PASSWORD = PASSWORD(...)</literal>
+ (for setting a user's password) and <literal>set names
+ default</literal> (for setting charset and collation).
</para>
<para>
@@ -254,22 +254,22 @@
</itemizedlist>
</listitem>
-
+
<listitem>
<para>
<literal>NDBCluster</literal>: A number of new or improved
error messages have been implemented in this release in order
to provide better and more accurate diagnostic information
regarding cluster configuration issues and problems. (Bug
- #11739, Bug #11749, Bug #12044, Bug #12786, Bug #13197)
+ #11739, Bug #11749, Bug #12044, Bug #12786, Bug #13197)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDBCluster</literal>: A new <quote>smart</quote> node
- allocation algorithm means that it is no longer necessary to use
- sequential IDs for cluster nodes, and that nodes not
+ allocation algorithm means that it is no longer necessary to
+ use sequential IDs for cluster nodes, and that nodes not
explicitly assigned IDs should now have IDs allocated
automatically in most cases. In practical terms, this means
that it is now possible to assign a set of node IDs such as
@@ -287,26 +287,28 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
An <literal>UPDATE</literal> query using a join would be
executed incorrectly on a replication slave. (Bug #12618)
</para>
</listitem>
-
+
<listitem>
<para>
Server crashed during a <literal>SELECT</literal> statement,
writing a message like this to the error log:
+
<programlisting>
InnoDB: Error: MySQL is trying to perform a SELECT
InnoDB: but it has not locked any tables in ::external_lock()!
</programlisting>
+
(Bug #12736)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDBCluster</literal>: <command>ndb_mgmd</command>
@@ -318,18 +320,18 @@
so. (Bug #13461)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDBCluster</literal>: Placing multiple <literal>[TCP
- DEFAULT]</literal> sections in the cluster
+ DEFAULT]</literal> sections in the cluster
<filename>config.ini</filename> file crashed
<command>ndb_mgmd</command>. (The <command>ndb_mgmd</command>
- process now exits gracefully with an appropriate error
- message instead.) (Bug #13611)
+ process now exits gracefully with an appropriate error message
+ instead.) (Bug #13611)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDBCluster</literal>: Trying to run
@@ -363,13 +365,13 @@
When calling a stored procedure with the syntax <literal>CALL
<replaceable>schema</replaceable>.<replaceable>procedurename</replaceable></literal>
and no default schema selected, <literal>ERROR 1046</literal>
- was displayed after the procedure returned. (Bug #13616)
+ was displayed after the procedure returned. (Bug #13616)
</para>
</listitem>
<listitem>
<para>
- With <option>--log-slave-updates</option>
+ With <option>--log-slave-updates</option>
<literal>Exec_master_log_pos</literal> of SQL thread lagged IO
(Bug #13023)
</para>
@@ -428,36 +430,37 @@
prohibition was not always enforced. (Bug #12935)
</para>
</listitem>
-
+
<listitem>
<para>
- <command>mysqlcheck <option>--all-databases</option>
- <option>--analyze</option> <option>--optimize</option></command>
- failed because it also tried to analyze and optimize the
+ <command>mysqlcheck <option>--all-databases</option>
+ <option>--analyze</option>
+ <option>--optimize</option></command> failed because it also
+ tried to analyze and optimize the
<literal>INFORMATION_SCHEMA</literal> tables which it can't.
(Bug #13783)
</para>
</listitem>
-
+
<listitem>
<para>
- <literal>SELECT * INTO OUTFILE ... FROM INFORMATION_SCHEMA.schemata</literal>
- failed with an <literal>Access denied</literal> error.
- (Bug #13202)
+ <literal>SELECT * INTO OUTFILE ... FROM
+ INFORMATION_SCHEMA.schemata</literal> failed with an
+ <literal>Access denied</literal> error. (Bug #13202)
</para>
</listitem>
-
+
<listitem>
<para>
- A table or view named Ç (C-cedilla) couldn't be dropped.
- (Bug #13145)
+ A table or view named Ç (C-cedilla) couldn't be dropped. (Bug
+ #13145)
</para>
</listitem>
-
+
<listitem>
<para>
- Tests containing <literal>SHOW TABLE STATUS</literal> failed on opnsrv6c.
- (Bug #14065)
+ Tests containing <literal>SHOW TABLE STATUS</literal> failed
+ on opnsrv6c. (Bug #14065)
</para>
</listitem>
@@ -576,13 +579,13 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
- <literal>NDBCluster</literal>: When performing a delete of
- a great many (tens of thousands of) rows at once from a
- Cluster table, an improperly dereferenced pointer could cause
- the <literal>mysqld</literal> process to crash. (Bug #9282)
+ <literal>NDBCluster</literal>: When performing a delete of a
+ great many (tens of thousands of) rows at once from a Cluster
+ table, an improperly dereferenced pointer could cause the
+ <literal>mysqld</literal> process to crash. (Bug #9282)
</para>
</listitem>
@@ -1240,12 +1243,12 @@
(Bug #12917)
</para>
</listitem>
-
+
<listitem>
<para>
- <command>mysqldump <replaceable>db_name</replaceable></command>
- didn't dump stored routines.
- (Bug #9056)
+ <command>mysqldump
+ <replaceable>db_name</replaceable></command> didn't dump
+ stored routines. (Bug #9056)
</para>
</listitem>
@@ -1658,24 +1661,53 @@
</para>
<itemizedlist>
-
+
+<!--
+see also 12943 in 5-0-13
+SQL:2003:
+Bug #6136
+Bug #6276
+Bug #6489
+Bug #6495
+Bug #6558
+Bug #9067
+Bug #9978
+Bug #10428
+Bug #10646
+Bug #10972
+
+Join precedence:
+Bug #4789
+Bug #12065
+Bug #13551
+
+Bug #12605?
+Bug #13832
+
+Bug #12816 requires following change:
+sql-syntax.sql: The following two clauses are semantically
+identical. (No longer true)
+-->
+
<listitem>
<para>
Natural joins and joins with <literal>USING</literal>,
including outer join variants, are now processed according to
the SQL:2003 standard. The changes include elimination of
redundant output columns specified in <literal>USING</literal>
- clauses and proper ordering of output columns. (Bug #4789, Bug
- #6136, Bug #6276, Bug #6489, Bug #6495, Bug #6558, Bug #9978,
- Bug #10646, Bug #10972, Bug #11710, Bug #13551)
+ clauses, proper ordering of output columns. (Bug #6136, Bug
+ #6276, Bug #6489, Bug #6495, Bug #6558, Bug #9067, Bug #9978,
+ Bug #10428, Bug #10646, Bug #10972.) The precedence of the
+ comma operator also now is lower compared to
+ <literal>JOIN</literal>. (Bug #4789, Bug #12065, Bug #13551.)
</para>
-
+
<para>
- This change may necessitate rewriting certain queries. For
- example, the following query will work as written before
- 5.0.12, but now will fail with an <literal>Unknown column
- 't1.id' in 'on clause'</literal> error:
- </para>
+ The change in precedence may necessitate rewriting certain
+ queries. For example, the following query will work as written
+ before 5.0.12, but now will fail with an <literal>Unknown
+ column 't1.id' in 'on clause'</literal> error:
+ </para>
<programlisting>
SELECT t1.id,t2.id,t3.id
@@ -1683,24 +1715,24 @@
LEFT JOIN t3 ON (t3.id=t1.id)
WHERE t1.id=t2.id;
</programlisting>
-
+
<para>
To rewrite the query, use parentheses to group the tables in
the inner join:
- </para>
-
+ </para>
+
<programlisting>
SELECT t1.id,t2.id,t3.id
FROM (t1,t2)
LEFT JOIN t3 ON (t3.id=t1.id)
WHERE t1.id=t2.id;
</programlisting>
-
+
<para>
For that particular query, it is also possible to rewrite it
as a natural join:
</para>
-
+
<programlisting>
SELECT t1.id,t2.id,t3.id
FROM t1,t2
@@ -1843,7 +1875,7 @@
Bugs fixed:
</para>
- <itemizedlist>
+ <itemizedlist>
<listitem>
<para>
@@ -1963,16 +1995,6 @@
<listitem>
<para>
- Natural joins and joins with <literal>USING</literal>,
- including outer join variants, now are processed according to
- the SQL:2003 standard. (Bug #4789, Bug #6136, Bug #6276, Bug
- #6495, Bug #6558, Bug #9978, Bug #10646, Bug #10972, Bug
- #11710)
- </para>
- </listitem>
-
- <listitem>
- <para>
It was not possible to create a stored function with a spatial
return value data type. (Bug #10499)
</para>
@@ -2156,9 +2178,9 @@
<listitem>
<para>
- <literal>ROW()</literal> function returned incorrect result
- when comparison involved <literal>NULL</literal> values. (Bug
- #12509)
+ The <literal>ROW()</literal> function returned an incorrect
+ result when comparison involved <literal>NULL</literal>
+ values. (Bug #12509)
</para>
</listitem>
@@ -2187,7 +2209,7 @@
<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.
+ as a join, even though the update updated only a single table.
(Bug #12569)
</para>
</listitem>
@@ -2337,25 +2359,25 @@
<listitem>
<para>
- Concatenating
- <literal>USER()</literal>/<literal>DATEBASE()</literal> with a
- column produces invalid results. (Bug #12351)
+ Concatenating <literal>USER()</literal> or
+ <literal>DATEBASE()</literal> with a column produced invalid
+ results. (Bug #12351)
</para>
</listitem>
<listitem>
<para>
Creating a view that included the
- <literal>TIMESTAMPDIFF()</literal> function resulted in
+ <literal>TIMESTAMPDIFF()</literal> function resulted in a
invalid view. (Bug #12298)
</para>
</listitem>
<listitem>
<para>
- Comparison of InnoDB multi-part primary keys that include
- <literal>VARCHAR</literal> columns can result in incorrect
- results. (Bug #12340)
+ Comparison of <literal>InnoDB</literal> multi-part primary
+ keys that include <literal>VARCHAR</literal> columns can
+ result in incorrect results. (Bug #12340)
</para>
</listitem>
@@ -2484,9 +2506,9 @@
<listitem>
<para>
- Columns defined as <literal>TINYINT(1)</literal> redefined as
- <literal>TINYINT(4)</literal> when incorporated into a
- <literal>VIEW</literal>. (Bug #11335)
+ Columns defined as <literal>TINYINT(1)</literal> were
+ redefined as <literal>TINYINT(4)</literal> when incorporated
+ into a <literal>VIEW</literal>. (Bug #11335)
</para>
</listitem>
Modified: trunk/xsl.d/expand-links.xsl
===================================================================
--- trunk/xsl.d/expand-links.xsl 2005-10-18 17:22:15 UTC (rev 79)
+++ trunk/xsl.d/expand-links.xsl 2005-10-18 19:38:21 UTC (rev 80)
@@ -2,10 +2,12 @@
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<!--
-expand-links.xsl
+expand-links.xsl - get rid of hyperlinks
+This transform is used when generating plain text files.
+
This is like an identity transform with the following exceptions:
-- <xref> elements the represent cross-references are resolved and
+- <xref> elements represent cross-references; they are resolved and
replaced with the proper text of the cross-reference.
- <ulink> elements are replaced with the link contents as described
below.
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r80 - in trunk: . refman-common xsl.d | paul | 18 Oct |
