List:Commits« Previous MessageNext Message »
From:paul Date:April 15 2008 3:48pm
Subject:svn commit - mysqldoc@docsrva: r10485 - in trunk: . dynamic-docs/changelog
View as plain text  
Author: paul
Date: 2008-04-15 17:48:06 +0200 (Tue, 15 Apr 2008)
New Revision: 10485

Log:


Modified:
   trunk/dynamic-docs/changelog/mysqld-1.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:30706
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:30751
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:30706
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:30753


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2008-04-15 15:07:21 UTC (rev 10484)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2008-04-15 15:48:06 UTC (rev 10485)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 394; 8237 bytes

@@ -15970,398 +15970,4 @@
 
   </logentry>
 
-  <logentry entrytype="bug">
-
-    <tags>
-      <manual type="triggers"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="32790"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.0.60"/>
-      <version ver="5.1.24"/>
-      <version ver="6.0.5"/>
-    </versions>
-
-    <message>
-
-      <para>
-        Incorrect assertions could cause a server crash for
-        <literal>DELETE</literal> triggers for transactional tables.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
-      <manual type="UPDATE"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="31747"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.23"/>
-    </versions>
-
-    <message>
-
-      <para>
-        For tables with certain definitions, <literal>UPDATE</literal>
-        statements could fail to find the correct record to update and
-        report an error when the record did in fact exist.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
-      <manual type="SHOW PROCESSLIST"/>
-      <manual type="Windows"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="30960"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.0.60"/>
-      <version ver="5.1.24"/>
-      <version ver="6.0.5"/>
-    </versions>
-
-    <message>
-
-      <para>
-        On WIndows, <literal>SHOW PROCESSLIST</literal> could display
-        process entries with a <literal>State</literal> value of
-        <literal>*** DEAD ***</literal>.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
-      <manual type="FEDERATED"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="35509"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.0.60"/>
-    </versions>
-
-    <message>
-
-      <para>
-        There was a memory leak when connecting to a
-        <literal>FEDERATED</literal> table using a connection string
-        that had a host value of <literal>localhost</literal> or omitted
-        the host and a port value of <literal>0</literal> or omitted the
-        port.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
-      <manual type="CREATE SERVER"/>
-      <manual type="ALTER SERVER"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="34790"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.24"/>
-      <version ver="6.0.5"/>
-    </versions>
-
-    <message>
-
-      <para>
-        <literal>CREATE SERVER</literal> and <literal>ALTER
-        SERVER</literal> could crash the server if out-of-memory
-        conditions occurred.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
-      <manual type="replication"/>
-      <manual type="InnoDB"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="35226"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.24"/>
-      <version ver="6.0.5"/>
-    </versions>
-
-    <message>
-
-      <para>
-        In some cases, <command>mysqld</command> would crash during
-        replication startup because <literal>InnoDB</literal> tried to
-        parse a <literal>NULL</literal> query and failed.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
-      <manual type="FEDERATED"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="28269"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.24"/>
-      <version ver="6.0.5"/>
-    </versions>
-
-    <message>
-
-      <para>
-        The <literal>FEDERATED</literal> storage engine did not perform
-        identifier quoting for column names that are reserved words when
-        sending statements to the remote server.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
-      <manual type="mysql.server"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="30378"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.0.60"/>
-      <version ver="5.1.24"/>
-      <version ver="6.0.5"/>
-    </versions>
-
-    <message>
-
-      <para>
-        An orphaned PID file from a no-longer-running process could
-        cause <command>mysql.server</command> to wait for that process
-        to exit even though it does not exist.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
-      <manual type="ucs2"/>
-      <manual type="MyISAM"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="32705"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.0.60"/>
-      <version ver="5.1.24"/>
-      <version ver="6.0.5"/>
-    </versions>
-
-    <message>
-
-      <para>
-        Inserting strings with a common prefix into a table that used
-        the <literal>ucs2</literal> character set corrupted the table.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
-      <manual type="MyISAM"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="33222"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.24"/>
-      <version ver="6.0.5"/>
-    </versions>
-
-    <message>
-
-      <para>
-        For <literal>MyISAM</literal> tables, <literal>CHECK
-        TABLE</literal> (non-<literal>QUICK</literal>) and any form of
-        <literal>REPAIR TABLE</literal> incorrected treated rows as
-        corrupted under the combination of the following conditions:
-      </para>
-
-      <itemizedlist>
-
-        <listitem>
-          <para>
-            The table had dynamic row format
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>
-            The table had a <literal>CHAR</literal> (not
-            <literal>VARCHAR</literal>) column longer than 127 bytes
-            (for multi-byte character sets this could be less than 127
-            characters)
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>
-            The table had rows with a signifcant length of more than 127
-            bytes significant length in that <literal>CHAR</literal>
-            column (that is, a byte beyond byte position 127 must be a
-            non-space character)
-          </para>
-        </listitem>
-
-      </itemizedlist>
-
-      <para>
-        This problem affected <literal>CHECK TABLE</literal>,
-        <literal>REPAIR TABLE</literal>, <literal>OPTIMIZE
-        TABLE</literal>, <literal>ALTER TABLE</literal>. <literal>CHECK
-        TABLE</literal> reported and marked the table as crashed if any
-        row was present that fulfilled the third condition. The other
-        statements deleted these rows.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
-      <manual type="plugins"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="33358"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.24"/>
-      <version ver="6.0.5"/>
-    </versions>
-
-    <message>
-
-      <para>
-        <literal>ENUM</literal>- or <literal>SET</literal>-valued plugin
-        variables could not be set from the command line.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
-      <manual type="INFORMATION_SCHEMA"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="34656"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.24"/>
-      <version ver="6.0.5"/>
-    </versions>
-
-    <message>
-
-      <para>
-        For debug builds, reading from
-        <literal>INFORMATION_SCHEMA.TABLES</literal> or
-        <literal>INFORMATION_SCHEMA.COLUMNS</literal> could cause
-        assertion failures. This could happen under rare circumstances
-        when <literal>INFORMATION_SCHEMA</literal> fails to get
-        information about a table (for example, when a connection is
-        killed).
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <bugs>
-      <fixes bugid="34726"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.24"/>
-      <version ver="6.0.5"/>
-    </versions>
-
-    <message>
-
-      <para>
-        A server running with the <option>--debug</option> option could
-        attempt to dereference a null pointer when opening tables,
-        resulting in a crash.
-      </para>
-
-    </message>
-
-  </logentry>
-
 </changelog>


Thread
svn commit - mysqldoc@docsrva: r10485 - in trunk: . dynamic-docs/changelogpaul15 Apr