Author: paul
Date: 2009-01-26 20:38:26 +0100 (Mon, 26 Jan 2009)
New Revision: 13385
Log:
r37801@frost: paul | 2009-01-26 13:39:05 -0500
Document bugfixes:
Bug#19424: InnoDB: Possibly a memory overrun of the buffer being freed (64-bit Visual C)
Modified:
trunk/dynamic-docs/changelog/mysqld.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:41130
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:37800
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:35928
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:41130
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:37801
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:35928
Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml 2009-01-26 19:38:19 UTC (rev 13384)
+++ trunk/dynamic-docs/changelog/mysqld.xml 2009-01-26 19:38:26 UTC (rev 13385)
Changed blocks: 21, Lines Added: 72, Lines Deleted: 80; 11392 bytes
@@ -7102,12 +7102,9 @@
<message>
<para>
- Use of
- <literal role="stmt">PREPARE</literal>
- and
- <literal role="stmt">EXECUTE</literal>
- with a statement that selected from a view in a subquery could
- cause a server crash.
+ Use of <literal role="stmt">PREPARE</literal> and
+ <literal role="stmt">EXECUTE</literal> with a statement that
+ selected from a view in a subquery could cause a server crash.
</para>
</message>
@@ -8050,10 +8047,9 @@
<message>
<para>
- Use of
- <literal role="stmt">PREPARE</literal>
- with a <literal role="stmt">CREATE PROCEDURE</literal> statement
- that contained a syntax error caused a server crash.
+ Use of <literal role="stmt">PREPARE</literal> with a
+ <literal role="stmt">CREATE PROCEDURE</literal> statement that
+ contained a syntax error caused a server crash.
</para>
</message>
@@ -13035,8 +13031,8 @@
<para>
For a debug server, a reference to an undefined user variable in
a prepared statement executed with
- <literal role="stmt">EXECUTE</literal>
- caused an assertion failure.
+ <literal role="stmt">EXECUTE</literal> caused an assertion
+ failure.
</para>
</message>
@@ -28366,11 +28362,9 @@
<para>
References to system variables in an SQL statement prepared with
- <literal role="stmt">PREPARE</literal>
- were evaluated during
- <literal role="stmt">EXECUTE</literal>
- to their values at prepare time, not to their values at
- execution time.
+ <literal role="stmt">PREPARE</literal> were evaluated during
+ <literal role="stmt">EXECUTE</literal> to their values at
+ prepare time, not to their values at execution time.
</para>
</message>
@@ -32385,13 +32379,11 @@
<message>
<para>
- Using
- <literal role="stmt">PREPARE</literal>
- to prepare a statement that invoked a stored routine that
- executed the prepared statement caused a <errortext>Packets out
- of order error</errortext> the second time the routine was
- invoked. This is prevented by disabling dynamic SQL within
- stored routines.
+ Using <literal role="stmt">PREPARE</literal> to prepare a
+ statement that invoked a stored routine that executed the
+ prepared statement caused a <errortext>Packets out of order
+ error</errortext> the second time the routine was invoked. This
+ is prevented by disabling dynamic SQL within stored routines.
</para>
<note>
@@ -39056,9 +39048,9 @@
<para>
Table creation for a <literal>MyISAM</literal> table failed if
<literal>DATA DIRECTORY</literal> or <literal>INDEX
- DIRECTORY</literal> options were given that specified the
- path name to the database directory where the table files would
- be created by default.
+ DIRECTORY</literal> options were given that specified the path
+ name to the database directory where the table files would be
+ created by default.
</para>
</message>
@@ -55610,12 +55602,11 @@
<para>
Previously, prepared statements processed using
- <literal role="stmt">PREPARE</literal>
- and
- <literal role="stmt">EXECUTE</literal>
- were not subject to caching in the query cache if they contained
- any <literal>?</literal> parameter markers. This limitation has
- been lifted.
+ <literal role="stmt">PREPARE</literal> and
+ <literal role="stmt">EXECUTE</literal> were not subject to
+ caching in the query cache if they contained any
+ <literal>?</literal> parameter markers. This limitation has been
+ lifted.
</para>
</message>
@@ -59051,12 +59042,10 @@
<para>
For the general query log, logging of prepared statements
executed via the C API differed from logging of prepared
- statements performed with
- <literal role="stmt">PREPARE</literal>
- and
- <literal role="stmt">EXECUTE</literal>.
- Logging for the latter was missing the
- <literal>Prepare</literal> and <literal>Execute</literal> lines.
+ statements performed with <literal role="stmt">PREPARE</literal>
+ and <literal role="stmt">EXECUTE</literal>. Logging for the
+ latter was missing the <literal>Prepare</literal> and
+ <literal>Execute</literal> lines.
</para>
</message>
@@ -65908,8 +65897,8 @@
<para>
<command>mysqld_safe</command> treated a relative path name
as relative to its own current working directory. Now it
- treats a relative path name as relative to the data directory
- (the same as <command>mysqld</command>).
+ treats a relative path name as relative to the data
+ directory (the same as <command>mysqld</command>).
</para>
</listitem>
@@ -84391,9 +84380,7 @@
<para>
The following statements now can be executed as prepared
- statements (using
- <literal role="stmt">PREPARE</literal>
- plus
+ statements (using <literal role="stmt">PREPARE</literal> plus
<literal role="stmt">EXECUTE</literal>):
</para>
@@ -85801,9 +85788,8 @@
<para>
<literal role="func">ROW_COUNT()</literal> returned an incorrect
- result after
- <literal role="stmt">EXECUTE</literal>
- of a prepared statement.
+ result after <literal role="stmt">EXECUTE</literal> of a
+ prepared statement.
</para>
</message>
@@ -87120,11 +87106,12 @@
</bugs>
<versions>
- <version ver="5.0.33"/>
<version ver="5.0.28"/>
+ <version ver="5.0.33"/>
+ <version ver="5.0.34"/>
</versions>
- <message>
+ <message ver="5.0.28,5.0.33">
<para>
<literal>InnoDB</literal>: Reduced optimization level for
@@ -87133,6 +87120,17 @@
</message>
+ <message ver="5.0.34">
+
+ <para>
+ <literal>InnoDB</literal>: Optimizations removed in MySQL 5.0.28
+ were re-enabled except for files under the
+ <literal>innobase/mem</literal> directory. (This is a
+ fine-tuning of optimization disabling.)
+ </para>
+
+ </message>
+
</logentry>
<logentry entrytype="bug">
@@ -91503,12 +91501,11 @@
Using prepared statements within a stored routine
(<literal role="stmt">PREPARE</literal>,
<literal role="stmt">EXECUTE</literal>,
- <literal role="stmt">DEALLOCATE
- PREPARE</literal>) could cause the client connection to be
- dropped after the routine returned. In addition, executing a
- statement which called a function deallocating the same
- statement caused the server to crash. This is prevented by
- disabling dynamic SQL within stored routines.
+ <literal role="stmt">DEALLOCATE PREPARE</literal>) could cause
+ the client connection to be dropped after the routine returned.
+ In addition, executing a statement which called a function
+ deallocating the same statement caused the server to crash. This
+ is prevented by disabling dynamic SQL within stored routines.
</para>
<note>
@@ -91525,11 +91522,10 @@
<para>
The restriction on the use of
<literal role="stmt">PREPARE</literal>,
- <literal role="stmt">EXECUTE</literal>,
- and
- <literal role="stmt">DEALLOCATE
- PREPARE</literal> within stored procedures was lifted. The
- restriction still applies to stored functions and triggers.
+ <literal role="stmt">EXECUTE</literal>, and
+ <literal role="stmt">DEALLOCATE PREPARE</literal> within stored
+ procedures was lifted. The restriction still applies to stored
+ functions and triggers.
</para>
</message>
@@ -93057,8 +93053,8 @@
<para>
<command>mysqld_safe</command> treated a relative path name as
relative to its own current working directory. Now it treats a
- relative path name as relative to the data directory (the same as
- <command>mysqld</command>).
+ relative path name as relative to the data directory (the same
+ as <command>mysqld</command>).
</para>
</message>
@@ -93472,10 +93468,9 @@
<para>
Special characters in database and table identifiers now are
- encoded when creating the corresponding directory names and
- file names. This relaxes the restrictions on the characters that
- can appear in identifiers. See
- <xref linkend="identifier-mapping"/>.
+ encoded when creating the corresponding directory names and file
+ names. This relaxes the restrictions on the characters that can
+ appear in identifiers. See <xref linkend="identifier-mapping"/>.
</para>
</message>
@@ -106467,8 +106462,7 @@
<para>
Passing a <literal role="type">DECIMAL</literal> value as a
parameter of a statement prepared with
- <literal role="stmt">PREPARE</literal>
- resulted in an error.
+ <literal role="stmt">PREPARE</literal> resulted in an error.
</para>
</message>
@@ -112618,11 +112612,11 @@
<message>
<para>
- For <literal>MERGE</literal> tables, avoid writing absolute
- path names in the <filename>.MRG</filename> file for the names of
- the constituent <literal>MyISAM</literal> tables so that if the
- data directory is moved, <literal>MERGE</literal> tables will
- not break. For <command>mysqld</command>, write just the
+ For <literal>MERGE</literal> tables, avoid writing absolute path
+ names in the <filename>.MRG</filename> file for the names of the
+ constituent <literal>MyISAM</literal> tables so that if the data
+ directory is moved, <literal>MERGE</literal> tables will not
+ break. For <command>mysqld</command>, write just the
<literal>MyISAM</literal> table name if it is in the same
database as the <literal>MERGE</literal> table, and a path
relative to the data directory otherwise. For the embedded
@@ -117145,8 +117139,8 @@
<para>
<command>myisamchk</command> and
<command>myisam_ftdump</command> should allow either table names
- or <filename>.MYI</filename> file names as arguments, but allowed
- only table names.
+ or <filename>.MYI</filename> file names as arguments, but
+ allowed only table names.
</para>
</message>
@@ -123463,11 +123457,9 @@
<para>
Corrected some failures of prepared statements for SQL
- (<literal role="stmt">PREPARE</literal>
- plus
- <literal role="stmt">EXECUTE</literal>)
- to return all rows for some
- <literal role="stmt">SELECT</literal> statements.
+ (<literal role="stmt">PREPARE</literal> plus
+ <literal role="stmt">EXECUTE</literal>) to return all rows for
+ some <literal role="stmt">SELECT</literal> statements.
</para>
</message>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r13385 - in trunk: . dynamic-docs/changelog | paul.dubois | 26 Jan |
