Author: mcbrown
Date: 2007-04-26 13:06:11 +0200 (Thu, 26 Apr 2007)
New Revision: 6204
Log:
Documenting Dev bugs:
Bug #27993
Bug #27962
Bug #27951
Bug #27895
Bug #27768
Bug #27767
Bug #26055
Bug #22181
Modified:
trunk/falcon/falcon-installation.xml
trunk/falcon/falcon-overview.xml
trunk/falcon/falcon.xml
trunk/falcon/news-falcon.xml
trunk/falcon/se-falcon.xml
Modified: trunk/falcon/falcon-installation.xml
===================================================================
--- trunk/falcon/falcon-installation.xml 2007-04-26 08:07:52 UTC (rev 6203)
+++ trunk/falcon/falcon-installation.xml 2007-04-26 11:06:11 UTC (rev 6204)
Changed blocks: 4, Lines Added: 207, Lines Deleted: 211; 17132 bytes
@@ -5,72 +5,72 @@
<!ENTITY % all.entities SYSTEM "all-entities.ent">
%all.entities;
]>
- <chapter id="building-falcon">
+<chapter id="building-falcon">
- <title>Getting and Building Falcon</title>
+ <title>Getting and Building Falcon</title>
- <para>
- Falcon has been made available as a special MySQL tree called
- <literal>mysql-6.0-falcon</literal>. In order to try out Falcon
- you must download the source code and build the special version of
- the MySQL tree.
- </para>
+ <para>
+ Falcon has been made available as a special MySQL tree called
+ <literal>mysql-6.0-falcon</literal>. In order to try out Falcon you
+ must download the source code and build the special version of the
+ MySQL tree.
+ </para>
- <para>
- To build the Falcon release you will need:
- </para>
+ <para>
+ To build the Falcon release you will need:
+ </para>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- GNU <command>make</command>
- </para>
- </listitem>
+ <listitem>
+ <para>
+ GNU <command>make</command>
+ </para>
+ </listitem>
- <listitem>
- <para>
- GNU <command>autoconf</command> 2.58 (or newer)
- </para>
- </listitem>
+ <listitem>
+ <para>
+ GNU <command>autoconf</command> 2.58 (or newer)
+ </para>
+ </listitem>
- <listitem>
- <para>
- GNU <command>automake</command> 1.8 (or newer)
- </para>
- </listitem>
+ <listitem>
+ <para>
+ GNU <command>automake</command> 1.8 (or newer)
+ </para>
+ </listitem>
- <listitem>
- <para>
- GNU <command>libtool</command> 1.5
- </para>
- </listitem>
+ <listitem>
+ <para>
+ GNU <command>libtool</command> 1.5
+ </para>
+ </listitem>
- </itemizedlist>
+ </itemizedlist>
- <para>
- You can obtain the sources for Falcon from
- <ulink
+ <para>
+ You can obtain the sources for Falcon from
+ <ulink
url="http://mysql.bkbits.com">http://mysql.bkbits.com</ulink>.
- In order to download the sources, you must use a BitKeeper client.
- You may use either the free client or the commercial client to
- download the sources.
- </para>
+ In order to download the sources, you must use a BitKeeper client.
+ You may use either the free client or the commercial client to
+ download the sources.
+ </para>
- <para>
- To obtain a source tree, first download and install the BitKeeper
- free client if you do not have it. The client can be obtained from
- <ulink url="http://www.bitmover.com/bk-client2.0.shar"/>. Your
- system will need to have <literal>gcc</literal>,
- <literal>make</literal>, <literal>patch</literal> and
- <literal>tar</literal> installed. <emphasis role="deprecated">Note
- that old 1.1 versions of the BitKeeper free client will not
- work!</emphasis>
- </para>
+ <para>
+ To obtain a source tree, first download and install the BitKeeper
+ free client if you do not have it. The client can be obtained from
+ <ulink url="http://www.bitmover.com/bk-client2.0.shar"/>. Your
+ system will need to have <literal>gcc</literal>,
+ <literal>make</literal>, <literal>patch</literal> and
+ <literal>tar</literal> installed. <emphasis role="deprecated">Note
+ that old 1.1 versions of the BitKeeper free client will not
+ work!</emphasis>
+ </para>
- <para>
- To install the BitKeeper client on Unix, use these commands:
- </para>
+ <para>
+ To install the BitKeeper client on Unix, use these commands:
+ </para>
<programlisting>
shell> <userinput>/bin/sh bk-client2.0.shar</userinput>
@@ -78,198 +78,194 @@
shell> <userinput>make</userinput>
</programlisting>
- <para>
- If you get a <literal>cc: command not found</literal> error,
- invoke this command when running <literal>make</literal>:
- </para>
+ <para>
+ If you get a <literal>cc: command not found</literal> error, invoke
+ this command when running <literal>make</literal>:
+ </para>
<programlisting>
shell> <userinput>make CC=gcc</userinput>
</programlisting>
- <para>
- This will create the tool <command>bkf</command>, the free
- BitKeeper client. For more information on the free BitKeeper
- client use:
- </para>
+ <para>
+ This will create the tool <command>bkf</command>, the free BitKeeper
+ client. For more information on the free BitKeeper client use:
+ </para>
<programlisting>shell> bkf --help</programlisting>
- <para>
- To install the BitKeeper client on Windows, use these
- instructions:
- </para>
+ <para>
+ To install the BitKeeper client on Windows, use these instructions:
+ </para>
- <orderedlist>
+ <orderedlist>
- <listitem>
- <para>
- Download and install Cygwin from
- <ulink url="http://cygwin.com/">http://cygwin.com</ulink>.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Download and install Cygwin from
+ <ulink url="http://cygwin.com/">http://cygwin.com</ulink>.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Make sure <command>gcc</command> and <command>make</command>
- have been installed under Cygwin. You can test this by issuing
- <command>which gcc</command> and <command>which make</command>
- commands. If either one is not installed, run Cygwin's package
- manager, select <command>gcc</command>,
- <command>make</command>, or both, and install them.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Make sure <command>gcc</command> and <command>make</command>
+ have been installed under Cygwin. You can test this by issuing
+ <command>which gcc</command> and <command>which make</command>
+ commands. If either one is not installed, run Cygwin's package
+ manager, select <command>gcc</command>, <command>make</command>,
+ or both, and install them.
+ </para>
+ </listitem>
- <listitem>
- <para>
- For the installation of the BitKeeper free client, use the
- same installations as given for Unix-like systems above.
- </para>
- </listitem>
-
- </orderedlist>
-
- <note>
+ <listitem>
<para>
- For more information using the public BitKeeper sources for
- MySQL, and the free BitKeeper client, see
- <xref linkend="installing-source-tree"/>.
+ For the installation of the BitKeeper free client, use the same
+ installations as given for Unix-like systems above.
</para>
- </note>
+ </listitem>
+ </orderedlist>
+
+ <note>
<para>
- After you have installed the BitKeeper client, you can access the
- MySQL development source tree:
+ For more information using the public BitKeeper sources for MySQL,
+ and the free BitKeeper client, see
+ <xref linkend="installing-source-tree"/>.
</para>
+ </note>
- <orderedlist>
+ <para>
+ After you have installed the BitKeeper client, you can access the
+ MySQL development source tree:
+ </para>
- <listitem>
- <para>
- Change location to the directory you want to work from, and
- then use the following command to make a local copy of the
- <literal>mysql-6.0-falcon</literal> tree:
- </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Change location to the directory you want to work from, and then
+ use the following command to make a local copy of the
+ <literal>mysql-6.0-falcon</literal> tree:
+ </para>
+
<programlisting>
shell> <userinput>bkf clone bk://mysql.bkbits.net/mysql-6.0-falcon mysql-6.0-falcon</userinput>
</programlisting>
- <para>
- In the preceding example, the source tree is set up in the
- <filename>mysql-6.0-falcon/</filename> subdirectory of your
- current directory.
- </para>
+ <para>
+ In the preceding example, the source tree is set up in the
+ <filename>mysql-6.0-falcon/</filename> subdirectory of your
+ current directory.
+ </para>
- <para>
- The initial download of the source tree may take a while,
- depending on the speed of your connection. Please be patient.
- </para>
- </listitem>
+ <para>
+ The initial download of the source tree may take a while,
+ depending on the speed of your connection. Please be patient.
+ </para>
+ </listitem>
- </orderedlist>
+ </orderedlist>
- <para>
- Once you have downloaded the Falcon tree:
- </para>
+ <para>
+ Once you have downloaded the Falcon tree:
+ </para>
- <orderedlist>
+ <orderedlist>
- <listitem>
- <para>
- Change into the directory containing the Falcon tree:
- </para>
+ <listitem>
+ <para>
+ Change into the directory containing the Falcon tree:
+ </para>
<programlisting>shell> cd mysql-6.0-falcon</programlisting>
- </listitem>
+ </listitem>
- <listitem>
- <para>
- Run the appropropriate build script to start the build
- process. For Pentium CPUs, use
- <command>compile-pentium-debug-falcon</command>, for AMD 64
- CPUs, use <command>compile-amd64-debug-falcon</command>. The
- build scipts are located in the <filename>BUILD</filename>,
- but they should be executed from the root directory of the
- tree:
- </para>
+ <listitem>
+ <para>
+ Run the appropropriate build script to start the build process.
+ For Pentium CPUs, use
+ <command>compile-pentium-debug-falcon</command>, for AMD 64
+ CPUs, use <command>compile-amd64-debug-falcon</command>. The
+ build scipts are located in the <filename>BUILD</filename>, but
+ they should be executed from the root directory of the tree:
+ </para>
<programlisting>shell> ./BUILD/compile-pentium-debug-falcon</programlisting>
- </listitem>
+ </listitem>
- <listitem>
- <para>
- The build script will create the necessary stubs for the
- configure process, run <command>configure</command>, and then
- execute the <command>make</command> to start the compilation
- process.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ The build script will create the necessary stubs for the
+ configure process, run <command>configure</command>, and then
+ execute the <command>make</command> to start the compilation
+ process.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Rather than installing directly from this build, you may want
- to create a binary package that can be distributed and
- relocated to the right location. To create such a
- distribution, use the
- <command>make_binary_distribution</command> script:
- </para>
+ <listitem>
+ <para>
+ Rather than installing directly from this build, you may want to
+ create a binary package that can be distributed and relocated to
+ the right location. To create such a distribution, use the
+ <command>make_binary_distribution</command> script:
+ </para>
<programlisting>shell> ./scripts/make_binary_distribution</programlisting>
- <para>
- The above command will create an archive with all the files
- you need configured to behave as if they were in a directoy
- named according to the version and tag for this release. For
- example, on a Linux Pentium machine, the Falcon release will
- create an archive with the name
- <filename>mysql-6.0.0-falcon-alpha-linux-i686.tar</filename>,
- which contains the directory
- <filename>mysql-6.0.0-falcon-alpha-linux-i686</filename>.
- </para>
+ <para>
+ The above command will create an archive with all the files you
+ need configured to behave as if they were in a directoy named
+ according to the version and tag for this release. For example,
+ on a Linux Pentium machine, the Falcon release will create an
+ archive with the name
+ <filename>mysql-6.0.0-falcon-alpha-linux-i686.tar</filename>,
+ which contains the directory
+ <filename>mysql-6.0.0-falcon-alpha-linux-i686</filename>.
+ </para>
- <para>
- To install the files to a new location, extract them
- specifying the new base directory:
- </para>
+ <para>
+ To install the files to a new location, extract them specifying
+ the new base directory:
+ </para>
<programlisting>shell> tar zxf mysql-6.0.0-falcon-alpha-linux-i686 -C /usr/local</programlisting>
- <para>
- You can either use directory or link to an alternative
- location. For example, you may want to create a link to
- <filename>/usr/local/mysql-falcon</filename>:
- </para>
+ <para>
+ You can either use directory or link to an alternative location.
+ For example, you may want to create a link to
+ <filename>/usr/local/mysql-falcon</filename>:
+ </para>
<programlisting>shell> cd /usr/local
shell> ln -s mysql-6.0.0-falcon-alpha-linux-i686 mysql-falcon</programlisting>
- </listitem>
+ </listitem>
- <listitem>
- <para>
- You must configure the new installation, including creating
- the base databases. Running <command>configure</command> in
- this directory will perform this function for you, and start
- an instance of <literal>mysqld</literal>:
- </para>
+ <listitem>
+ <para>
+ You must configure the new installation, including creating the
+ base databases. Running <command>configure</command> in this
+ directory will perform this function for you, and start an
+ instance of <literal>mysqld</literal>:
+ </para>
<programlisting>shell> cd mysql-falcon
shell> ./configure</programlisting>
- <para>
- If <literal>mysqld</literal> fails to start, ensure that the
- files in your chosen directory are owned by the
- <literal>mysql</literal> user:
- </para>
+ <para>
+ If <literal>mysqld</literal> fails to start, ensure that the
+ files in your chosen directory are owned by the
+ <literal>mysql</literal> user:
+ </para>
<programlisting>shell> chown -R mysql:mysql *</programlisting>
- </listitem>
+ </listitem>
- <listitem>
- <para>
- Confirm that <command>mysqld</command> is running by obtaining
- the version from the server:
- </para>
+ <listitem>
+ <para>
+ Confirm that <command>mysqld</command> is running by obtaining
+ the version from the server:
+ </para>
<programlisting>shell> ./bin/mysqladmin version
./bin/mysqladmin Ver 8.42 Distrib 6.0.0-falcon-alpha, for pc-linux-gnu on i686
@@ -286,21 +282,21 @@
Threads: 1 Questions: 1 Slow queries: 0 Opens: 14 Flush tables: 1 »
Open tables: 7 Queries per second avg: </programlisting>
- <para>
- You may need to update your <literal>LD_LIBRARY_PATH</literal>
- with the MySQL libraries:
- </para>
+ <para>
+ You may need to update your <literal>LD_LIBRARY_PATH</literal>
+ with the MySQL libraries:
+ </para>
<programlisting>shell> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/mysql-falcon/lib</programlisting>
- </listitem>
+ </listitem>
- </orderedlist>
+ </orderedlist>
- <para>
- Once Falcon has been installed, you can try creating tables using
- the Falcon engine. For example, to create a simple table with
- Falcon:
- </para>
+ <para>
+ Once Falcon has been installed, you can try creating tables using
+ the Falcon engine. For example, to create a simple table with
+ Falcon:
+ </para>
<programlisting>shell> ./bin/mysql
Welcome to the MySQL monitor. Commands end with ; or \g.
@@ -314,15 +310,15 @@
mysql> CREATE TABLE falcon_basic (id int, fname varchar(20)) ENGINE=Falcon;
Query OK, 0 rows affected (1.07 sec)</programlisting>
- <para>
- For more information on Falcon features and functionality, see
- <xref
+ <para>
+ For more information on Falcon features and functionality, see
+ <xref
linkend="se-falcon"/>. You may want to exchange
- information on your experiences with other users on the
- <ulink
+ information on your experiences with other users on the
+ <ulink
url="http://forums.mysql.com/list.php?133">Falcon
- Forum</ulink>. If you think you have found a bug, use
- <ulink url="http://buys.mysql.com">MySQL Bugs</ulink>.
- </para>
+ Forum</ulink>. If you think you have found a bug, use
+ <ulink url="http://buys.mysql.com">MySQL Bugs</ulink>.
+ </para>
- </chapter>
+</chapter>
Modified: trunk/falcon/falcon-overview.xml
===================================================================
--- trunk/falcon/falcon-overview.xml 2007-04-26 08:07:52 UTC (rev 6203)
+++ trunk/falcon/falcon-overview.xml 2007-04-26 11:06:11 UTC (rev 6204)
Changed blocks: 3, Lines Added: 10, Lines Deleted: 7; 1566 bytes
@@ -15,9 +15,9 @@
information from the physical store of the data. Other storage
engines available for MySQL include <xref linkend="innodb"/> and
<xref
- linkend="myisam-storage-engine"/>. For more information on storage
- engines for MySQL, see <xref linkend="storage-engines"/>. For more
- detail on MySQL, see the <xref linkend="top"/>.
+ linkend="myisam-storage-engine"/>. For more information
+ on storage engines for MySQL, see <xref linkend="storage-engines"/>.
+ For more detail on MySQL, see the <xref linkend="top"/>.
</para>
<para>
@@ -112,8 +112,8 @@
<listitem>
<para>
- Intelligent disk management automatically manages data
- files and extensions. Space within log and data files is
+ Intelligent disk management automatically manages data files
+ and extensions. Space within log and data files is
automatically reclaimed and reused.
</para>
</listitem>
@@ -133,8 +133,11 @@
</itemizedlist>
-<para>You can test out the Falcon storage engine using the <link
- linkend="mysql-query-browser">MySQL Query Browser</link>.</para>
+ <para>
+ You can test out the Falcon storage engine using the
+ <link
+ linkend="mysql-query-browser">MySQL Query Browser</link>.
+ </para>
</section>
Modified: trunk/falcon/falcon.xml
===================================================================
--- trunk/falcon/falcon.xml 2007-04-26 08:07:52 UTC (rev 6203)
+++ trunk/falcon/falcon.xml 2007-04-26 11:06:11 UTC (rev 6204)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 6; 1156 bytes
@@ -50,16 +50,18 @@
<para>
Falcon is currently an Alpha release and should not be used in
production environments. Falcon is currently only supported within
- a special fork of the MySQL release, termed MySQL-6.0-falcon.
- This release is not considered ready for production. The
+ a special fork of the MySQL release, termed MySQL-6.0-falcon. This
+ release is not considered ready for production. The
mysql-6.0-falcon tree is provided only for testing and evaluation
of the Falcon storage engine.
</para>
- <note> <para>
- Thet mysql-6.0-falcon tree may not include all feature or bug
- fixes that have been applied to previous releases of MySQL.
- </para></note>
+ <note>
+ <para>
+ Thet mysql-6.0-falcon tree may not include all feature or bug
+ fixes that have been applied to previous releases of MySQL.
+ </para>
+ </note>
</preface>
Modified: trunk/falcon/news-falcon.xml
===================================================================
--- trunk/falcon/news-falcon.xml 2007-04-26 08:07:52 UTC (rev 6203)
+++ trunk/falcon/news-falcon.xml 2007-04-26 11:06:11 UTC (rev 6204)
Changed blocks: 3, Lines Added: 266, Lines Deleted: 172; 15283 bytes
@@ -7,15 +7,20 @@
]>
<appendix id="news-falcon">
- <title>Changes in MySQL 5.2 Falcon</title>
+ <title>Changes in MySQL 6.0 Falcon</title>
- <para>
- An overview of the changes in the MySQL 5.2 Falcon release sequence.
- </para>
+ <note>
+ <para>
+ Prior to MySQL 5.24 Falcon Alpha (April 13th, 2007), all Falcon
+ releases were based on the MySQL 5.2 tree. All new releases after
+ this version and data, including related bugs and other changes,
+ apply to the MySQL 6.0 Falcon tree.
+ </para>
+ </note>
- <section id="news-falcon-5-2-4">
+ <section>
- <title>Changes in release 5.2.4 (Not yet released)</title>
+ <title>Changes in release 6.0.0 (Not yet released)</title>
<para>
Bugs fixed:
@@ -25,208 +30,295 @@
<listitem>
<para>
- Continually updating a <literal>BLOB</literal> column would
- cause MySQL server to crash. (Bug #27719)
+ Rolling back an inserted row while accessing the same on a
+ different connection would cause a crash. (Bug #27993)
</para>
</listitem>
<listitem>
<para>
- Using a trigger on an <literal>UPDATE</literal> to a Falcon
- table when autocommit is disabled would cause MySQL server to
- crash. (Bug #27574)
+ Creating a table with a 19 digit <literal>DECIMAL</literal>
+ column would cause incorrect data to be stored. This is due to
+ current limitation in Falcon where you cannot create a table
+ with a column with greateer than 18 digits precision (i.e.
+ <literal>DECIMAL(18,9)</literal>). Creating a column with
+ larger than this specification will fail and raise an error.
+ (Bug #27962)
</para>
</listitem>
<listitem>
<para>
- Using <literal>ROLLBACK</literal> after a
- <literal>DELETE</literal> does not restore the deleted row.
- (Bug #27357)
+ Executing <literal>INSERT INTO ... SELECT FROM</literal> could
+ cause a crash on large data sets. (Bug #27951)
</para>
</listitem>
<listitem>
<para>
- Row insertions to a table with long <literal>VARCHAR</literal>
- columns and large compound indexes would cause MySQL to crash.
- (Bug #26850)
+ Inserting data into the same table on two different
+ connections with autocommit disabled would cause a crash. (Bug
+ #27895)
</para>
</listitem>
<listitem>
<para>
- Falcon could consume large amounts of memory during a high
- number of continuous <literal>INSERT</literal> statements.
- (Bug #26843)
+ Creating a Falcon table immediately after creating a new
+ database could cause a crash. (Bug #27768)
</para>
</listitem>
<listitem>
<para>
- Updating a partitioned table in two sessions simultaneously
- would cause MySQL to crash. (Bug #26828)
+ Executing <literal>SELECT ... FOR UPDATE</literal> in a second
+ connection on a newly created and populated table could cause
+ a crash. (Bug #27767)
</para>
</listitem>
<listitem>
<para>
- Locking between sessions when using <literal>SELECT ... FOR
- UPDATE</literal> would not work. (Bug #26826)
+ Deleting a large quantity of rows in a single table may result
+ in <literal>ERROR 1020</literal>. (Bug #26055)
</para>
</listitem>
<listitem>
<para>
- Searching for records in a table with a
- <literal>decimal(6,6)</literal> column would fail to find the
- value. (Bug #26469)
+ Running <literal>SELECT</literal> after a changing the table
+ contents does not result in a new dataset. (Bug #22181)
</para>
</listitem>
- <listitem>
- <para>
- Rows with a numeric column may fail to find records with zero
- values. (Bug #26468)
- </para>
- </listitem>
+ </itemizedlist>
- <listitem>
- <para>
- Tables with a long multi-column index may fail to find a
- record for <literal>UPDATE</literal>. (Bug #26420)
- </para>
- </listitem>
+ </section>
- <listitem>
- <para>
- Tables with <literal>UNIQUE</literal> key constraints would
- not be enforced. (Bug #26803)
- </para>
- </listitem>
+ <section id="news-falcon-5-2">
- <listitem>
- <para>
- Opening the same database with Falcon tables on a different
- connection could cause a crash. (Bug #27428)
- </para>
- </listitem>
+ <title>Changes in MysQL 5.2 Falcon</title>
- <listitem>
- <para>
- Interrupting a stored procedure during execution could cause a
- crash. (Bug #27539)
- </para>
- </listitem>
+ <para>
+ An overview of the changes in the MySQL 5.2 Falcon release
+ sequence.
+ </para>
- <listitem>
- <para>
- Two simultaneous <literal>SELECT ... FOR UPDATE</literal>
- statements with <literal>READ-COMMITTED</literal> isolation
- level would result in the wrong error message being returned.
- (Bug #26871)
- </para>
- </listitem>
+ <section id="news-falcon-5-2-4">
- <listitem>
- <para>
- When updating a table with a unique key constraint the
- constraint would not be enforced. (Bug #26802)
- </para>
- </listitem>
+ <title>Changes in release 5.2.4 (Not released)</title>
- <listitem>
- <para>
- Executing <literal>DROP TABLE</literal> on a table that has
- been created using <literal>CREATE TABLE ... SELECT</literal>.
- (Bug #25564)
- </para>
- </listitem>
+ <para>
+ Bugs fixed:
+ </para>
- <listitem>
- <para>
- Retrieving rows from a table that used an index would
- sometimes fail to return the row. (Bug #26452)
- </para>
- </listitem>
+ <itemizedlist>
- <listitem>
- <para>
- Random updates of <literal>LONG VARCHAR</literal> columns
- would fail. (Bug #23818)
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Continually updating a <literal>BLOB</literal> column would
+ cause MySQL server to crash. (Bug #27719)
+ </para>
+ </listitem>
- </itemizedlist>
+ <listitem>
+ <para>
+ Using a trigger on an <literal>UPDATE</literal> to a Falcon
+ table when autocommit is disabled would cause MySQL server
+ to crash. (Bug #27574)
+ </para>
+ </listitem>
- </section>
+ <listitem>
+ <para>
+ Using <literal>ROLLBACK</literal> after a
+ <literal>DELETE</literal> does not restore the deleted row.
+ (Bug #27357)
+ </para>
+ </listitem>
- <section id="news-falcon-5-2-3">
+ <listitem>
+ <para>
+ Row insertions to a table with long
+ <literal>VARCHAR</literal> columns and large compound
+ indexes would cause MySQL to crash. (Bug #26850)
+ </para>
+ </listitem>
- <title>Changes in release 5.2.3 (15 February 2007)</title>
+ <listitem>
+ <para>
+ Falcon could consume large amounts of memory during a high
+ number of continuous <literal>INSERT</literal> statements.
+ (Bug #26843)
+ </para>
+ </listitem>
- <para>
- Bugs fixed:
- </para>
+ <listitem>
+ <para>
+ Updating a partitioned table in two sessions simultaneously
+ would cause MySQL to crash. (Bug #26828)
+ </para>
+ </listitem>
- <itemizedlist>
+ <listitem>
+ <para>
+ Locking between sessions when using <literal>SELECT ... FOR
+ UPDATE</literal> would not work. (Bug #26826)
+ </para>
+ </listitem>
- <listitem>
- <para>
- MySQL would crash with an assertion on startup during recovery
- referring to <filename>tc.log</filename>. (Bug #26161)
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Searching for records in a table with a
+ <literal>decimal(6,6)</literal> column would fail to find
+ the value. (Bug #26469)
+ </para>
+ </listitem>
- <listitem>
- <para>
- A crash would occur when running <literal>UPDATE</literal>
- within a loop inside a stored procedure. (Bug #25537)
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Rows with a numeric column may fail to find records with
+ zero values. (Bug #26468)
+ </para>
+ </listitem>
- </itemizedlist>
+ <listitem>
+ <para>
+ Tables with a long multi-column index may fail to find a
+ record for <literal>UPDATE</literal>. (Bug #26420)
+ </para>
+ </listitem>
- </section>
+ <listitem>
+ <para>
+ Tables with <literal>UNIQUE</literal> key constraints would
+ not be enforced. (Bug #26803)
+ </para>
+ </listitem>
- <section id="news-falcon-5-2-2">
+ <listitem>
+ <para>
+ Opening the same database with Falcon tables on a different
+ connection could cause a crash. (Bug #27428)
+ </para>
+ </listitem>
- <title>Changes in release 5.2.2 (not released)</title>
+ <listitem>
+ <para>
+ Interrupting a stored procedure during execution could cause
+ a crash. (Bug #27539)
+ </para>
+ </listitem>
- <para>
- Bugs fixed:
- </para>
+ <listitem>
+ <para>
+ Two simultaneous <literal>SELECT ... FOR UPDATE</literal>
+ statements with <literal>READ-COMMITTED</literal> isolation
+ level would result in the wrong error message being
+ returned. (Bug #26871)
+ </para>
+ </listitem>
- <itemizedlist>
+ <listitem>
+ <para>
+ When updating a table with a unique key constraint the
+ constraint would not be enforced. (Bug #26802)
+ </para>
+ </listitem>
- <listitem>
- <para>
- MySQL would fail with an assertion on startup. (Bug #25835)
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Executing <literal>DROP TABLE</literal> on a table that has
+ been created using <literal>CREATE TABLE ...
+ SELECT</literal>. (Bug #25564)
+ </para>
+ </listitem>
- </itemizedlist>
+ <listitem>
+ <para>
+ Retrieving rows from a table that used an index would
+ sometimes fail to return the row. (Bug #26452)
+ </para>
+ </listitem>
- </section>
+ <listitem>
+ <para>
+ Random updates of <literal>LONG VARCHAR</literal> columns
+ would fail. (Bug #23818)
+ </para>
+ </listitem>
- <section id="news-falcon-5-2-1">
+ </itemizedlist>
- <title>Changes in release 5.2.1 (not released)</title>
+ </section>
- <para>
- Functionality added or changed
- </para>
+ <section id="news-falcon-5-2-3">
- <itemizedlist>
+ <title>Changes in release 5.2.3 (15 February 2007)</title>
- <listitem>
- <para>
- Performance improvements: thread bottleneckes have been
- reduced when a larger number of parallel auto-commit threads
- executed a trivial query in a hard loop.
- </para>
- </listitem>
+ <para>
+ Bugs fixed:
+ </para>
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ MySQL would crash with an assertion on startup during
+ recovery referring to <filename>tc.log</filename>. (Bug
+ #26161)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A crash would occur when running <literal>UPDATE</literal>
+ within a loop inside a stored procedure. (Bug #25537)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+ <section id="news-falcon-5-2-2">
+
+ <title>Changes in release 5.2.2 (not released)</title>
+
+ <para>
+ Bugs fixed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ MySQL would fail with an assertion on startup. (Bug #25835)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+ <section id="news-falcon-5-2-1">
+
+ <title>Changes in release 5.2.1 (not released)</title>
+
+ <para>
+ Functionality added or changed
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Performance improvements: thread bottleneckes have been
+ reduced when a larger number of parallel auto-commit threads
+ executed a trivial query in a hard loop.
+ </para>
+ </listitem>
+
<!--
<listitem>
<para>
@@ -238,49 +330,51 @@
</listitem>
-->
- </itemizedlist>
+ </itemizedlist>
- <para>
- Bugs fixed:
- </para>
+ <para>
+ Bugs fixed:
+ </para>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- Between fails with Unicode field. (Bug #24511)
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Between fails with Unicode field. (Bug #24511)
+ </para>
+ </listitem>
- <listitem>
- <para>
- Crash if create index on nullable <literal>utf8</literal>
- column. (Bug #25555)
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Crash if create index on nullable <literal>utf8</literal>
+ column. (Bug #25555)
+ </para>
+ </listitem>
- <listitem>
- <para>
- MySQL crashes during <literal>DROP TABLE</literal> after
- <literal>CREATE TABLE ... SELECT *</literal>. (Bug #25564)
- </para>
- </listitem>
+ <listitem>
+ <para>
+ MySQL crashes during <literal>DROP TABLE</literal> after
+ <literal>CREATE TABLE ... SELECT *</literal>. (Bug #25564)
+ </para>
+ </listitem>
- <listitem>
- <para>
- Assertion when killing a <literal>CREATE TABLE ...
- SELECT</literal> statement. (Bug #25565)
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Assertion when killing a <literal>CREATE TABLE ...
+ SELECT</literal> statement. (Bug #25565)
+ </para>
+ </listitem>
- <listitem>
- <para>
- Falcon compound primary key problem. (Bug #25828)
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Falcon compound primary key problem. (Bug #25828)
+ </para>
+ </listitem>
- </itemizedlist>
+ </itemizedlist>
+ </section>
+
</section>
</appendix>
Modified: trunk/falcon/se-falcon.xml
===================================================================
--- trunk/falcon/se-falcon.xml 2007-04-26 08:07:52 UTC (rev 6203)
+++ trunk/falcon/se-falcon.xml 2007-04-26 11:06:11 UTC (rev 6204)
Changed blocks: 4, Lines Added: 21, Lines Deleted: 7; 2069 bytes
@@ -6,12 +6,15 @@
%all.entities;
]>
<chapter id="se-falcon">
-<title>Using Falcon</title>
- <para>This chapter contains information on using Falcon, including
- configuration parameters, detals on how Falcon works internally and the
- limitations of the current release. </para>
+ <title>Using Falcon</title>
+ <para>
+ This chapter contains information on using Falcon, including
+ configuration parameters, detals on how Falcon works internally and
+ the limitations of the current release.
+ </para>
+
<section id="se-falcon-configuration">
<title>Configuration Parameters</title>
@@ -27,6 +30,7 @@
</para>
<itemizedlist>
+
<!--
<listitem>
<para>
@@ -208,9 +212,9 @@
Two further files contain the on-disk copy of the Falcon serial
log. These are also created within the realm of the corresponding
database. In a future release, you will be able to specify an
- alternate location for these log files. So with the preceding example
- data file <filename>test.fts</filename> the log files will be
- named <filename>test.fl1</filename> and
+ alternate location for these log files. So with the preceding
+ example data file <filename>test.fts</filename> the log files will
+ be named <filename>test.fl1</filename> and
<filename>test.fl2</filename>.
</para>
@@ -811,6 +815,16 @@
<listitem>
<para>
+ Falcon is currently limited to to support
+ <literal>DECIMAL</literal> columns with a maximum 18 digits
+ and 9 digits precision (<literal>DECIMAL(18,9)</literal>).
+ Creating a table with a specification larger than this will
+ raise an error.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Lock timeout configuration is not supported.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6204 - trunk/falcon | mcbrown | 26 Apr |
