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.3460 05/09/02 12:41:00 paul@stripped +4 -0
TRUNCATE TABLE now always resets
AUTO_INCREMENT counter for InnoDB tables.
refman/sql-syntax.xml
1.59 05/09/02 12:40:57 paul@stripped +7 -3
TRUNCATE TABLE now always resets
AUTO_INCREMENT counter for InnoDB tables.
refman-5.1/sql-syntax.xml
1.32 05/09/02 12:40:57 paul@stripped +7 -3
Sync.
refman-5.0/sql-syntax.xml
1.34 05/09/02 12:40:57 paul@stripped +7 -3
Sync.
refman-common/news-5.0.xml
1.136 05/09/02 12:29:24 paul@stripped +13 -0
Document bugfix. (Bug #11946)
refman-common/news-5.0.xml
1.135 05/09/02 12:24:03 paul@stripped +50 -45
Move some more-important items up in their list.
refman-common/news-5.0.xml
1.134 05/09/02 11:53:30 paul@stripped +61 -0
Document bugfix. (Bug #12820)
# 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: frost.snake.net
# Root: /Volumes/frost2/MySQL/bk/mysqldoc
--- 1.31/refman-5.1/sql-syntax.xml 2005-09-02 08:18:36 -05:00
+++ 1.32/refman-5.1/sql-syntax.xml 2005-09-02 12:40:57 -05:00
@@ -8800,10 +8800,14 @@
For <literal>InnoDB</literal> before version 5.0.3,
<literal>TRUNCATE TABLE</literal> is mapped to
<literal>DELETE</literal>, so there is no difference. Starting
- with MySQL/InnoDB-5.0.3, fast <literal>TRUNCATE TABLE</literal>
- is available. The operation is still mapped to
+ with MySQL 5.0.3, fast <literal>TRUNCATE TABLE</literal> is
+ available. However, the operation is still mapped to
<literal>DELETE</literal> if there are foreign key constraints
- that reference the table.
+ that reference the table. (When fast truncate is used, it resets
+ any <literal>AUTO_INCREMENT</literal> counter. From MySQL 5.0.13
+ on, the <literal>AUTO_INCREMENT</literal> counter is reset by
+ <literal>TRUNCATE TABLE</literal>, regardless of whether there
+ is a foreign key constraint.)
</para>
<para>
--- 1.133/refman-common/news-5.0.xml 2005-09-01 13:33:14 -05:00
+++ 1.136/refman-common/news-5.0.xml 2005-09-02 12:29:24 -05:00
@@ -175,6 +175,19 @@
<listitem>
<para>
+ <literal>InnoDB</literal>: The <literal>TRUNCATE
+ TABLE</literal> statement for <literal>InnoDB</literal> tables
+ always resets the counter for an
+ <literal>AUTO_INCREMENT</literal> column now, regardless of
+ whether there is a foreign key constraint on the table.
+ (Beginning with 5.0.3, <literal>TRUNCATE TABLE</literal> reset
+ the counter, but only if there was no such constraint.) (Bug
+ #11946)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The <literal>LEAST()</literal> and
<literal>GREATEST()</literal> functions used to return
<literal>NULL</literal> only if all arguments were
@@ -194,6 +207,67 @@
<listitem>
<para>
+ The Windows installer made a change to one of the
+ <literal>mysql.proc</literal> table files, causing stored
+ routine functionality to be compromised. The Windows installer
+ now never overwrites files in the MySQL data directory. During
+ an upgrade from one version to another, a file in the data
+ directory will not be overwritten even if it has not been
+ modified since it was put there by an older installer. (Bug
+ #12820)
+ </para>
+
+ <para>
+ If you have already lost access to stored routines because of
+ this problem, you can get them back using the following
+ procedure:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Stop the server.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In the <filename>mysql\data</filename> directory under
+ your MySQL installation directory, and replace the
+ <filename>proc.frm</filename> file with corresponding file
+ from the version of MySQL that you were using before you
+ upgraded.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Start the server
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Start the <command>mysql</command> command-line client
+ (use the <literal>root</literal> account or another
+ account that has full database privileges) and execute the
+ <filename>mysql_fix_privilege_tables.sql</filename> script
+ that upgrades the grant tables to the current structure.
+ Instructions for doing this are given in
+ <xref linkend="upgrading-grant-tables"/>.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ After this, all stored routine functionality should work.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
On Windows, the server was preventing tables from being
created if the table name was a prefix of a forbidden name.
For example, <literal>nul</literal> is a forbidden name
@@ -5351,35 +5425,10 @@
<itemizedlist>
- <listitem>
- <para>
- Added the <literal>engine_condition_pushdown</literal> system
- variable. For NDB, setting this variable to 1 allows
- processing of some <literal>WHERE</literal> clause conditions
- to be processed in NDB nodes before rows are sent to the MySQL
- server, rather than having rows sent to the server for
- evaluation.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Additional control over transaction completion was
- implemented. The <literal>COMMIT</literal> and
- <literal>ROLLBACK</literal> statements support <literal>AND
- [NO] CHAIN</literal> and <literal>RELEASE</literal> clauses.
- There is a new <literal>RELEASE SAVEPOINT</literal> statement.
- The <literal>completion_type</literal> system variable was
- added for setting the global and session default completion
- type.
- </para>
- </listitem>
-
- <listitem>
- <para>
- New privilege <literal>CREATE USER</literal> was added.
- </para>
- </listitem>
+ <remark>
+ Leave any security fix items first in the list so they stand out
+ better
+ </remark>
<listitem>
<para>
@@ -5429,6 +5478,52 @@
<listitem>
<para>
+ InnoDB: <emphasis role="bold">Upgrading from 4.1:</emphasis>
+ The sorting order for end-space in <literal>TEXT</literal>
+ columns for InnoDB tables has changed. Starting from 5.0.3,
+ InnoDB compares <literal>TEXT</literal> columns as
+ space-padded at the end. If you have a non-unique index on a
+ <literal>TEXT</literal> column, you should run <literal>CHECK
+ TABLE</literal> on it, and run <literal>OPTIMIZE
+ TABLE</literal> if the check reports errors. If you have a
+ <literal>UNIQUE INDEX</literal> on a <literal>TEXT</literal>
+ column, you should rebuild the table with <literal>OPTIMIZE
+ TABLE</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Added the <literal>engine_condition_pushdown</literal> system
+ variable. For NDB, setting this variable to 1 allows
+ processing of some <literal>WHERE</literal> clause conditions
+ to be processed in NDB nodes before rows are sent to the MySQL
+ server, rather than having rows sent to the server for
+ evaluation.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Additional control over transaction completion was
+ implemented. The <literal>COMMIT</literal> and
+ <literal>ROLLBACK</literal> statements support <literal>AND
+ [NO] CHAIN</literal> and <literal>RELEASE</literal> clauses.
+ There is a new <literal>RELEASE SAVEPOINT</literal> statement.
+ The <literal>completion_type</literal> system variable was
+ added for setting the global and session default completion
+ type.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A new <literal>CREATE USER</literal> privilege was added.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<filename>my.cnf</filename> in the compile-time datadir
(usually <filename>/usr/local/mysql/data/</filename> in the
binary tarball distributions) is not being read anymore. The
@@ -5539,22 +5634,6 @@
to specify a single option other than
<option>--defaults-file</option> following the service name.
This is for compatibility with MySQL 4.1. (Bug #7856)
- </para>
- </listitem>
-
- <listitem>
- <para>
- InnoDB: <emphasis role="bold">Upgrading from 4.1:</emphasis>
- The sorting order for end-space in <literal>TEXT</literal>
- columns for InnoDB tables has changed. Starting from 5.0.3,
- InnoDB compares <literal>TEXT</literal> columns as
- space-padded at the end. If you have a non-unique index on a
- <literal>TEXT</literal> column, you should run <literal>CHECK
- TABLE</literal> on it, and run <literal>OPTIMIZE
- TABLE</literal> if the check reports errors. If you have a
- <literal>UNIQUE INDEX</literal> on a <literal>TEXT</literal>
- column, you should rebuild the table with <literal>OPTIMIZE
- TABLE</literal>.
</para>
</listitem>
--- 1.58/refman/sql-syntax.xml 2005-09-02 08:18:04 -05:00
+++ 1.59/refman/sql-syntax.xml 2005-09-02 12:40:57 -05:00
@@ -8921,10 +8921,14 @@
For <literal>InnoDB</literal> before version 5.0.3,
<literal>TRUNCATE TABLE</literal> is mapped to
<literal>DELETE</literal>, so there is no difference. Starting
- with MySQL/InnoDB-5.0.3, fast <literal>TRUNCATE TABLE</literal>
- is available. The operation is still mapped to
+ with MySQL 5.0.3, fast <literal>TRUNCATE TABLE</literal> is
+ available. However, the operation is still mapped to
<literal>DELETE</literal> if there are foreign key constraints
- that reference the table.
+ that reference the table. (When fast truncate is used, it resets
+ any <literal>AUTO_INCREMENT</literal> counter. From MySQL 5.0.13
+ on, the <literal>AUTO_INCREMENT</literal> counter is reset by
+ <literal>TRUNCATE TABLE</literal>, regardless of whether there
+ is a foreign key constraint.)
</para>
<para>
--- 1.33/refman-5.0/sql-syntax.xml 2005-09-02 08:18:31 -05:00
+++ 1.34/refman-5.0/sql-syntax.xml 2005-09-02 12:40:57 -05:00
@@ -8800,10 +8800,14 @@
For <literal>InnoDB</literal> before version 5.0.3,
<literal>TRUNCATE TABLE</literal> is mapped to
<literal>DELETE</literal>, so there is no difference. Starting
- with MySQL/InnoDB-5.0.3, fast <literal>TRUNCATE TABLE</literal>
- is available. The operation is still mapped to
+ with MySQL 5.0.3, fast <literal>TRUNCATE TABLE</literal> is
+ available. However, the operation is still mapped to
<literal>DELETE</literal> if there are foreign key constraints
- that reference the table.
+ that reference the table. (When fast truncate is used, it resets
+ any <literal>AUTO_INCREMENT</literal> counter. From MySQL 5.0.13
+ on, the <literal>AUTO_INCREMENT</literal> counter is reset by
+ <literal>TRUNCATE TABLE</literal>, regardless of whether there
+ is a foreign key constraint.)
</para>
<para>
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (paul:1.3460) | paul | 2 Sep |
