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.3116 05/07/25 15:03:28 Mike.Hillyer@stripped +4 -0
Document bugfixes 10986, 6903, 11311, 11213, 11227, 10407, 11414, 10736, 10794, 11522, 11639, 11543, 11709, 11399
Add 5.0.11 section to changelog files.
Add skeleton Makefile to refman-common to support make %.reformat.
refman-common/Makefile
1.1 05/07/25 15:03:27 Mike.Hillyer@stripped +29 -0
refman/titles.ent
1.36 05/07/25 15:03:27 Mike.Hillyer@stripped +1 -0
Add entry for 5.0.11 changelog.
refman-common/news-5.0.xml
1.3 05/07/25 15:03:27 Mike.Hillyer@stripped +113 -4
Document Bugfixes. Add 5.0.11 section.
refman-common/news-4.1.xml
1.3 05/07/25 15:03:27 Mike.Hillyer@stripped +51 -7
Document Bugfixes.
refman-common/Makefile
1.0 05/07/25 15:03:27 Mike.Hillyer@stripped +0 -0
BitKeeper file /home/mysqldoc/mysqldoc2/refman-common/Makefile
# 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/mysqldoc2
--- New file ---
+++ refman-common/Makefile 05/07/25 15:03:27
# Makefile for MySQL Reference Manual
# Location of repository root relative to current directory
REPO_ROOT = ..
# Location of directory containing Makefile components
MAKE_DIR = $(REPO_ROOT)/make.d
all::
@echo "You must say what you want to do."
@echo "Some commands supported by this Makefile:"
@echo " make clean"
@echo " make doc_name.html"
@echo " make doc_name.pdf"
@echo " make doc_name.txt"
# Import standard variables and target rules
# Need xml-html-dir for formatting the manual itself into a subdir,
# but also need xml-html for formatting ReadMe.html
include $(MAKE_DIR)/vars-layout
include $(MAKE_DIR)/vars-shell
include $(MAKE_DIR)/vars-docbook
include $(MAKE_DIR)/xml-valid
include $(MAKE_DIR)/xml-format
CHAPTERFMT = ./chapterfmt.pl
GT = $(TOOLS_DIR)/generate-text-files.pl
--- 1.2/refman-common/news-4.1.xml 2005-07-24 20:22:54 -06:00
+++ 1.3/refman-common/news-4.1.xml 2005-07-25 15:03:27 -06:00
@@ -190,6 +190,22 @@
<listitem>
<para>
+ Incorrect error message displayed if user attempted to create
+ a table in a non-existing database using <literal>CREATE
+ database_name.table_name</literal> syntax. (Bug #10407)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>LPAD()</literal> and <literal>RPAD()</literal>
+ functions returned the wrong length to
+ <literal>mysql_fetch_fields()</literal>. (Bug #11311)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The C API function <literal>mysql_statement_reset()</literal>
did not clear error information. (Bug #11183)
</para>
@@ -505,6 +521,35 @@
<listitem>
<para>
+ A <literal>ROLLUP</literal> query could return a wrong result
+ set when its <literal>GROUP BY</literal> clause contained
+ references to the same column. (Bug #11543)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Queries with subqueries in the <literal>FROM</literal> clause
+ were not being added to the query cache. (Bug #11522)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Possible crash on Windows when performing GROUP BY on a
+ calculated field. (Bug #11414)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>mysql_config</literal> script did not handle
+ symbolic linking properly. (Bug #10986)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
When used within a subquery, <literal>SUBSTRING()</literal>
returned an empty string. (Bug #10269)
</para>
@@ -1290,11 +1335,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>
@@ -3065,8 +3109,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.2/refman-common/news-5.0.xml 2005-07-24 20:22:54 -06:00
+++ 1.3/refman-common/news-5.0.xml 2005-07-25 15:03:27 -06:00
@@ -163,6 +163,60 @@
for each individual 5.0.x release.
</para>
+ <section id="news-5-0-11">
+
+ <title id="title-news-5-0-11">&title-news-5-0-11;</title>
+
+ <para>
+ Functionality added or changed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Added new <literal>ER_STACK_OVERRUN_NEED_MORE</literal> error
+ message to indicate that, while the stack is not completly
+ full, more stack space is required. (Bug #11213)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ Bugs fixed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ The <literal>LPAD()</literal> and <literal>RPAD()</literal>
+ functions returned the wrong length to
+ <literal>mysql_fetch_fields()</literal>. (Bug #11311)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A <literal>UNIQUE VARCHAR</literal> column would be
+ mis-identified as <literal>MUL</literal> in table
+ descriptions. (Bug #11227)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Incorrect error message displayed if user attempted to create
+ a table in a non-existing database using <literal>CREATE
+ database_name.table_name</literal> syntax. (Bug #10407)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
<section id="news-5-0-10">
<title id="title-news-5-0-10">&title-news-5-0-10;</title>
@@ -289,6 +343,24 @@
<listitem>
<para>
+ Aliasing the column names in a <literal>VIEW</literal> did not
+ work when executing a <literal>SELECT</literal> query on the
+ <literal>VIEW</literal>. (Bug #11399)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Performing an <literal>ORDER BY</literal> on a
+ <literal>SELECT</literal> from a <literal>VIEW</literal>
+ produced unexpected results when <literal>VIEW</literal> and
+ underlying table had the same column name on different
+ columns. Bug #11709)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The C API function <literal>mysql_statement_reset()</literal>
did not clear error information. (Bug #11183)
</para>
@@ -703,6 +775,28 @@
<listitem>
<para>
+ <literal>SHOW CREATE VIEW</literal> did not take the
+ <literal>ANSI MODE</literal> into account when quoting
+ identifiers. (Bug #6903)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>mysql_config</literal> script did not handle
+ symbolic linking properly. (Bug #10986)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Incorrect results when using <literal>GROUP BY ... WITH
+ ROLLUP</literal> on a <literal>VIEW</literal>. (Bug #11639)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Instances of the <literal>VAR_SAMP()</literal> function in
view definitions were converted to
<literal>VARIANCE()</literal>. This is incorrect because
@@ -943,6 +1037,21 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ Combining cursors and subselects could cause server crash or
+ memory leaks. (Bug #10736)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If a prepared statement cursor is opened but not completely
+ fetched, attempting to open a cursor for a second prepared
+ statement will fail. (Bug #10794)
+ </para>
+ </listitem>
+
</itemizedlist>
</section>
@@ -3453,8 +3562,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>
@@ -4327,8 +4436,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.35/refman/titles.ent 2005-07-23 12:15:31 -06:00
+++ 1.36/refman/titles.ent 2005-07-25 15:03:27 -06:00
@@ -1,6 +1,7 @@
<?xml version='1.0' encoding='utf-8'?>
<!ENTITY top "MySQL Reference Manual"><!-- "MySQL Reference Manual" -->
<!ENTITY current-version "5.0.9-beta"><!-- "5.0.9-beta" --><!-- Current MySQL Version - update with new releases -->
+<!ENTITY title-news-5-0-11 "Changes in release 5.0.11 (Not yet released)"><!-- "Changes in release 5.0.11 (Not yet released)" -->
<!ENTITY title-news-5-0-10 "Changes in release 5.0.10 (Not yet released)"><!-- "Changes in release 5.0.10 (Not yet released)" -->
<!ENTITY title-news-5-0-9 "Changes in release 5.0.9 (15 July 2005)"><!-- "Changes in release 5.0.9 (Not yet released)" -->
<!ENTITY title-news-4-0-9 "Changes in release 4.0.9 (09 Jan 2003)"><!-- "Changes in release 4.0.9 (09 Jan 2003)" -->
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (Mike.Hillyer:1.3116) | mhillyer | 25 Jul |
