svn commit - mysqldoc@docsrva: r12947 - trunk/dynamic-docs/changelog

[martin.brown]

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 @@
   <logentry entrytype="bug">
 
     <tags>
+      <manual type="falcon"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="39789"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.9"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Recovery of a tablespace for <literal>FALCON</literal> tables
+        could fail if the tablespace was already in use.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="falcon"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="40994"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.9"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Unique indexes on <literal>FALCON</literal> tables can not be
+        created when the the column is <literal>NOT NULL</literal>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="falcon"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="40614"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.9"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Date values of <literal>000-00-00</literal> inserted into a
+        <literal>FALCON</literal> table were incorrectly recognized and
+        returned when performing a <literal>SELECT</literal> on a field
+        with an index.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="falcon"/>
+      <manual type="innodb"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="29246"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.9"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Searching for text values on a column using a character set that
+        provides multi-weight characters and sequences on an
+        <literal>INNODB</literal> or <literal>FALCON</literal>
table
+        with an index would fail to find the expanded value.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="falcon"/>
+      <manual type="build"/>
+      <manual type="mac os
+            x"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="41270"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.8"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Compiling using <option>--with-falcon</option> on Mac OS X fails
+        if you use <literal>CXX=gcc</literal>. You must specify that the
+        <command>g++</command> compiler should be used for C++ using
+        <literal>CXX=g++</literal>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="falcon"/>
+      <manual type="build"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="39419"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.9"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Compiling MySQL with <literal>FALCON</literal> support enabled
+        with a compiler that does not support exceptions would fail to
+        complete successfully. <command>configure</command> has been
+        updated to switch off <literal>FALCON</literal> support if the
+        specified compiler does not support exceptions.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="falcon"/>
+      <manual type="build"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="39260"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.9"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Starting MySQL with <literal>FALCON</literal> 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:
+      </para>
+
+<programlisting>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</programlisting>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="falcon"/>
+      <manual type="build"/>
+      <manual type="solaris
+            9"/>
+      <manual type="SPARC"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="37622"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.9"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Compiling MySQL with <literal>FALCON</literal> support enabled
+        on Solaris 9 using the Sun Studio compiler would fail with
+        error:
+      </para>
+
+<programlisting>"Interlock.h", line 149: Error: #error cas not defined. We
need>= Solaris 10.</programlisting>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="falcon"/>
+      <manual type="tablespace"/>
+      <manual
+            type="partition"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="39702"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.9"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Creating a <literal>FALCON</literal> 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.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="falcon"/>
+      <manual type="index"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="40112"/>
+      <fixes bugid="40130"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.8"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The indexes and record contents of a <literal>FALCON</literal>
+        table could get out of synchronization during a lrge number of
+        updates. Because <literal>FALCON</literal> 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 <literal>SELECT</literal>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="falcon"/>
+      <manual type="column"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="40158"/>
+      <fixes bugid="39388"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.8"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Creating a table, or selecting from a table using the
+        <literal>FALCON</literal> storage engine and with a double quote
+        in the name would cause an assertion failure.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="falcon"/>
+      <manual type="tablespace"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="40302"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.9"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Creation of a tablespace file within <literal>FALCON</literal>
+        could create a tablespace entry in the
+        <literal>INFORMATION_SCHEMA.FALCON_TABLESPACE_IO</literal> even
+        the underlying data file had not been created.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="falcon"/>
+      <manual type="tablespace"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="36804"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.9"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The <literal>FALCON</literal> storage would silently recreate
+        missing tablespace files if they did not exist. Errors are now
+        written to the MySQL error log when the
+        <literal>FALCON</literal> 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.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="falcon"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="39708"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.8"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When creating a table with the <literal>FALCON</literal> 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.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
       <highlight type="clusterapi"/>
       <manual type="NdbScanFilter"/>
       <manual type="BIT"/>