From: Date: December 13 2008 10:44am
Subject: svn commit - mysqldoc@docsrva: r12947 - trunk/dynamic-docs/changelog
List-Archive: http://lists.mysql.com/commits/61576
Message-Id: <200812130944.mBD9ieq4029641@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Author: mcbrown
Date: 2008-12-13 10:44:40 +0100 (Sat, 13 Dec 2008)
New Revision: 12947
Log:
Documenting Bug Fixes:
Bug #29246
Bug #35503
Bug #36631
Bug #36804
Bug #37622
Bug #38541
Bug #38567
Bug #38569
Bug #39260
Bug #39388
Bug #39419
Bug #39456
Bug #39694
Bug #39695
Bug #39696
Bug #39702
Bug #39708
Bug #39789
Bug #40112
Bug #40130
Bug #40158
Bug #40302
Bug #40614
Bug #40690
Bug #40691
Bug #40700
Bug #40893
Bug #40994
Bug #41231
Bug #41270
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-12-13 03:29:20 UTC (rev 12946)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-12-13 09:44:40 UTC (rev 12947)
Changed blocks: 1, Lines Added: 404, Lines Deleted: 0; 8785 bytes
@@ -9,6 +9,410 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Recovery of a tablespace for FALCON tables
+ could fail if the tablespace was already in use.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Unique indexes on FALCON tables can not be
+ created when the the column is NOT NULL.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Date values of 000-00-00 inserted into a
+ FALCON table were incorrectly recognized and
+ returned when performing a SELECT on a field
+ with an index.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Searching for text values on a column using a character set that
+ provides multi-weight characters and sequences on an
+ INNODB or FALCON table
+ with an index would fail to find the expanded value.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Compiling using on Mac OS X fails
+ if you use CXX=gcc. You must specify that the
+ g++ compiler should be used for C++ using
+ CXX=g++.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Compiling MySQL with FALCON support enabled
+ with a compiler that does not support exceptions would fail to
+ complete successfully. configure has been
+ updated to switch off FALCON support if the
+ specified compiler does not support exceptions.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Starting MySQL with FALCON support when MySQL
+ has not been compiled with a compiler supporting exceptions
+ would lead to strange errors and results. MySQL will now fail to
+ initialize if you have compiled without exceptions enabled with
+ the following message:
+
+
+081116 12:21:12 [ERROR] Falcon must be compiled with C++ exceptions enabled to work. Please adjust your compile flags.
+[Falcon] Error: Falcon exiting process
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Compiling MySQL with FALCON support enabled
+ on Solaris 9 using the Sun Studio compiler would fail with
+ error:
+
+
+"Interlock.h", line 149: Error: #error cas not defined. We need>= Solaris 10.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Creating a FALCON table while specifying a
+ specific tablespace and partition to be used for the table will
+ fail if the specified tablespace does not already exist,
+ returning a error indicating general table creation failure. The
+ message has been updated to indicate that the failure is due to
+ nonexistent tablespace.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The indexes and record contents of a FALCON
+ table could get out of synchronization during a lrge number of
+ updates. Because FALCON returns data only if
+ it matches both the index and record data the result sets
+ returned could be invalid when comparing the results of an index
+ and non-index based SELECT.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Creating a table, or selecting from a table using the
+ FALCON storage engine and with a double quote
+ in the name would cause an assertion failure.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Creation of a tablespace file within FALCON
+ could create a tablespace entry in the
+ INFORMATION_SCHEMA.FALCON_TABLESPACE_IO even
+ the underlying data file had not been created.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The FALCON storage would silently recreate
+ missing tablespace files if they did not exist. Errors are now
+ written to the MySQL error log when the
+ FALCON system tablespace files are found to
+ be missing. Warnings are produce in the log file when attempting
+ to access data tablespace files that do not exist.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ When creating a table with the FALCON engine
+ where the size of the key in the index was larger than supported
+ (the error message did not signify the severity of the problem.
+ The message and error has been updated.
+
+
+
+
+
+
+
+
+