Below is the list of changes that have just been committed into a local
mysqldoc repository of root. When root 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.3553 05/09/13 17:06:53 Mike.Hillyer@stripped +6 -0
Document Bugs: 11707,11296,12363,9948,12905
refman/mysql-database-administration.xml
1.82 05/09/13 17:06:51 Mike.Hillyer@stripped +15 -1
Update refman options as per bug fixes.
refman-common/news-5.0.xml
1.171 05/09/13 17:06:51 Mike.Hillyer@stripped +51 -4
Document Bugfixes
refman-common/news-4.1.xml
1.91 05/09/13 17:06:51 Mike.Hillyer@stripped +38 -8
Document Bugfixes
refman-5.1/mysql-database-administration.xml
1.41 05/09/13 17:06:51 Mike.Hillyer@stripped +15 -1
Sync
refman-5.0/mysql-database-administration.xml
1.42 05/09/13 17:06:51 Mike.Hillyer@stripped +15 -1
Sync
refman-4.1/mysql-database-administration.xml
1.68 05/09/13 17:06:50 Mike.Hillyer@stripped +5 -2
Sync
# 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: Mike.Hillyer
# Host: www.openwin.org
# Root: /home/mysqldoc/mysqldoc
--- 1.40/refman-5.1/mysql-database-administration.xml 2005-09-13 08:27:38 -06:00
+++ 1.41/refman-5.1/mysql-database-administration.xml 2005-09-13 17:06:51 -06:00
@@ -1000,12 +1000,25 @@
<para>
The port number to use when listening for TCP/IP
- connections.
+ connections. The port number must be
+ <literal>1024</literal> or higher unless MySQL is run as
+ the <literal>root</literal> system user.
</para>
</listitem>
<listitem>
<para>
+ <option>--skip-character-set-client-handshake</option>
+ </para>
+
+ <para>
+ Ignore character set information sent by the client and use the default server character set.
+ This option makes MySQL 4.1 and higher behave like MySQL 4.0.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<option>--socket=<replaceable>path</replaceable></option>
</para>
@@ -7745,6 +7758,7 @@
<para>
<literal>one_shot</literal>
</para>
+
<para>
This is not a variable, but it can be used when setting
some variables. It's described in
--- 1.90/refman-common/news-4.1.xml 2005-09-13 08:32:44 -06:00
+++ 1.91/refman-common/news-4.1.xml 2005-09-13 17:06:51 -06:00
@@ -165,7 +165,20 @@
Functionality added or changed:
</para>
-<!-- REPLACE WITH <itemizedlist> WHEN THERE ARE ITEMS FOR THIS LIST -->
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ A new command line argument was added to mysqld to ignore
+ client character set information sent during handshake, and
+ use server side settings instead, to reproduce 4.0 behaviour
+ (Bug #9948):
+
+<programlisting>mysqld --skip-character-set-client-handshake</programlisting>
+ </para>
+ </listitem>
+
+ </itemizedlist>
<para>
Bugs fixed:
@@ -180,6 +193,24 @@
<listitem>
<para>
+ <literal>CHECKSUM TABLE</literal> command returned
+ <literal>0</literal> for tables with deleted rows. After
+ upgrading, users who used stored checksum information to
+ detect table changes should rebuild their checksum data. (Bug
+ #12296)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The value of <literal>character_set_results</literal> could be
+ set to <literal>NULL</literal>, but returned the string
+ <literal>"NULL"</literal> when retrieved. (Bug #12363)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>GROUP_CONCAT()</literal> ignored an empty string if
it was the first value to occur in the result. (Bug #12863)
</para>
@@ -2126,11 +2157,10 @@
and isolation level of the transaction is not set to
serializable then <literal>InnoDB</literal> uses a consistent
read for select in clauses like <literal>INSERT
- INTO…SELECT</literal> and
- <literal>UPDATE…(SELECT)</literal> that do not specify
- <literal>FOR UPDATE</literal> or <literal>IN SHARE
- MODE</literal>. Thus no locks are set to rows read from
- selected table.
+ INTO…SELECT</literal> and <literal>UPDATE…(SELECT)</literal>
+ that do not specify <literal>FOR UPDATE</literal> or
+ <literal>IN SHARE MODE</literal>. Thus no locks are set to
+ rows read from selected table.
</para>
</listitem>
@@ -3920,8 +3950,8 @@
<listitem>
<para>
InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>,
- single table <literal>UPDATE…SELECT</literal> and single
- table <literal>DELETE…SELECT</literal> clauses when
+ single table <literal>UPDATE…SELECT</literal> and single table
+ <literal>DELETE…SELECT</literal> clauses when
<literal>innodb_locks_unsafe_for_binlog</literal> is used and
isolation level of the transaction is not serializable.
<literal>InnoDB</literal> uses consistent read in these cases
--- 1.170/refman-common/news-5.0.xml 2005-09-13 14:44:34 -06:00
+++ 1.171/refman-common/news-5.0.xml 2005-09-13 17:06:51 -06:00
@@ -175,6 +175,17 @@
<listitem>
<para>
+ A new command line argument was added to mysqld to ignore
+ client character set information sent during handshake, and
+ use server side settings instead, to reproduce 4.0 behaviour
+ (Bug #9948):
+
+<programlisting>mysqld --skip-character-set-client-handshake</programlisting>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>OPTIMIZE TABLE</literal> now is prohibited in stored
procedures and functions and in triggers. (Bug #12953)
</para>
@@ -212,6 +223,16 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ Reorder network startup to come after all other
+ initialization, particularly storage engine startup which can
+ take a long time. This also prevents MySQL from being run on a
+ privileged port (any port under 1024) unless run as the root
+ user. (Bug #11707)
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
@@ -222,6 +243,22 @@
<listitem>
<para>
+ <literal>SHOW FIELDS FROM
+ <replaceable>schemaname</replaceable>.<replaceable>viewname</replaceable></literal>
+ caused error 1046 when no default schema was set. (Bug #12905)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The value of <literal>character_set_results</literal> could be
+ set to <literal>NULL</literal>, but returned the string
+ <literal>"NULL"</literal> when retrieved. (Bug #12363)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>InnoDB</literal>: Limit recursion depth to 200 in
deadlock detection to avoid running out of stack space. (Bug
#12588)
@@ -771,6 +808,16 @@
<listitem>
<para>
+ <literal>CHECKSUM TABLE</literal> command returned
+ <literal>0</literal> for tables with deleted rows. After
+ upgrading, users who used stored checksum information to
+ detect table changes should rebuild their checksum data. (Bug
+ #12296)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A data type of <literal>CHAR BINARY</literal> was not
recognized as valid for stored routine parameters. (Bug #9048)
</para>
@@ -5353,8 +5400,8 @@
InnoDB: True <literal>VARCHAR</literal>: InnoDB stored the
'position' of a row wrong in a column prefix primary key
index; this could cause MySQL to complain <literal>ERROR 1032:
- Can't find record …</literal> in an update of the primary
- key, and also some <literal>ORDER BY</literal> or
+ Can't find record …</literal> in an update of the primary key,
+ and also some <literal>ORDER BY</literal> or
<literal>DISTINCT</literal> queries. (Bug #9314)
</para>
</listitem>
@@ -6256,8 +6303,8 @@
<listitem>
<para>
InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>,
- single table <literal>UPDATE…SELECT</literal> and single
- table <literal>DELETE…SELECT</literal> clauses when
+ single table <literal>UPDATE…SELECT</literal> and single table
+ <literal>DELETE…SELECT</literal> clauses when
<literal>innodb_locks_unsafe_for_binlog</literal> is used and
isolation level of the transaction is not serializable.
<literal>InnoDB</literal> uses consistent read in these cases
--- 1.67/refman-4.1/mysql-database-administration.xml 2005-09-13 08:27:30 -06:00
+++ 1.68/refman-4.1/mysql-database-administration.xml 2005-09-13 17:06:50 -06:00
@@ -1021,10 +1021,12 @@
<para>
The port number to use when listening for TCP/IP
- connections.
+ connections. The port number must be
+ <literal>1024</literal> or higher unless MySQL is run as
+ the <literal>root</literal> system user.
</para>
</listitem>
-
+
<listitem>
<para>
<option>--socket=<replaceable>path</replaceable></option>
@@ -6425,6 +6427,7 @@
<para>
<literal>one_shot</literal>
</para>
+
<para>
This is not a variable, but it can be used when setting
some variables. It's described in
--- 1.81/refman/mysql-database-administration.xml 2005-09-13 08:26:27 -06:00
+++ 1.82/refman/mysql-database-administration.xml 2005-09-13 17:06:51 -06:00
@@ -1014,12 +1014,25 @@
<para>
The port number to use when listening for TCP/IP
- connections.
+ connections. The port number must be
+ <literal>1024</literal> or higher unless MySQL is run as
+ the <literal>root</literal> system user.
</para>
</listitem>
<listitem>
<para>
+ <option>--skip-character-set-client-handshake</option>
+ </para>
+
+ <para>
+ Ignore character set information sent by the client and use the default server character set.
+ This option makes MySQL 4.1 and higher behave like MySQL 4.0.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<option>--socket=<replaceable>path</replaceable></option>
</para>
@@ -8052,6 +8065,7 @@
<para>
<literal>one_shot</literal>
</para>
+
<para>
This is not a variable, but it can be used when setting
some variables. It's described in
--- 1.41/refman-5.0/mysql-database-administration.xml 2005-09-13 08:27:34 -06:00
+++ 1.42/refman-5.0/mysql-database-administration.xml 2005-09-13 17:06:51 -06:00
@@ -1000,12 +1000,25 @@
<para>
The port number to use when listening for TCP/IP
- connections.
+ connections. The port number must be
+ <literal>1024</literal> or higher unless MySQL is run as
+ the <literal>root</literal> system user.
</para>
</listitem>
<listitem>
<para>
+ <option>--skip-character-set-client-handshake</option>
+ </para>
+
+ <para>
+ Ignore character set information sent by the client and use the default server character set.
+ This option makes MySQL 4.1 and higher behave like MySQL 4.0.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<option>--socket=<replaceable>path</replaceable></option>
</para>
@@ -7753,6 +7766,7 @@
<para>
<literal>one_shot</literal>
</para>
+
<para>
This is not a variable, but it can be used when setting
some variables. It's described in
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (Mike.Hillyer:1.3553) | mhillyer | 14 Sep |
