| List: | Commits | « Previous MessageNext Message » | |
| From: | jon | Date: | November 7 2007 8:37pm |
| Subject: | svn commit - mysqldoc@docsrva: r8570 - trunk/dynamic-docs/changelog | ||
| View as plain text | |||
Author: jstephens Date: 2007-11-07 20:37:03 +0100 (Wed, 07 Nov 2007) New Revision: 8570 Log: Consolidated more redundant changelog entries. Modified: trunk/dynamic-docs/changelog/dupes.txt trunk/dynamic-docs/changelog/mysqld.xml Modified: trunk/dynamic-docs/changelog/dupes.txt =================================================================== --- trunk/dynamic-docs/changelog/dupes.txt 2007-11-07 18:50:35 UTC (rev 8569) +++ trunk/dynamic-docs/changelog/dupes.txt 2007-11-07 19:37:03 UTC (rev 8570) Changed blocks: 6, Lines Added: 42, Lines Deleted: 40; 1188 bytes @@ -136,42 +136,43 @@ 16614x 16674x 16695x -16861 -17047 -17208 -17501 -17526 -17582 -17605 -17667 -17671 -17810 +16861x +17047x +17208x +17501x +17526x +17582x +17605x +17667x +17671x +17810x 17857x -17876 -17926 +17876x +17926x +18005x 18091x -18283 -18298 +18283x +18298x 18359x -18361 -18385 -18386 -18472 -18516 -18628 -18676 -18912 -18934 -18997 -19022 -19136 +18361x +18385x +18386x +18472x +18516x +18628x +18676x +18912x +18934x +18997x +19022x +19136x 19182x -19201 -19288 -19370 -19542 -19645 -19690 +19201x +19288x +19370x +19542x +19645x +19690x 19733x 19764 19815 @@ -179,13 +180,14 @@ 19978 20073 20166 -20384 -20403 +20384x +20403x 20446 20535 -20579 +20579x 20612 -20783 +20783x +20836x 20872 21007 21013 @@ -204,7 +206,7 @@ 21671 21690 21726 -21789 +21789x 21868 21948 22060x @@ -214,7 +216,7 @@ 22773 22823 22937 -23044 +23044x 23256 23404 23409 @@ -243,7 +245,7 @@ 25059 25090 25239 -25422 +25422x 25530 25578 25621 @@ -351,7 +353,7 @@ 29102 29103 29118 -29129 +29129x 29167 29176 29185 Modified: trunk/dynamic-docs/changelog/mysqld.xml =================================================================== --- trunk/dynamic-docs/changelog/mysqld.xml 2007-11-07 18:50:35 UTC (rev 8569) +++ trunk/dynamic-docs/changelog/mysqld.xml 2007-11-07 19:37:03 UTC (rev 8570) Changed blocks: 76, Lines Added: 222, Lines Deleted: 1008; 40141 bytes @@ -5720,35 +5720,7 @@ <logentry entrytype="bug"> - <tags> - <manual type="TRIM"/> - <manual type="EXPLAIN EXTENDED"/> - </tags> - <bugs> - <fixes bugid="17526"/> - </bugs> - - <versions> - <version ver="4.1.22"/> - </versions> - - <message> - - <para> - Using the extended syntax for - <function role="sql">TRIM()</function> — that is, - <literal>TRIM(... FROM ...)</literal> — caused erroneous - output from <literal>EXPLAIN EXTENDED</literal> statements. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <bugs> <fixes bugid="18750"/> </bugs> @@ -14022,41 +13994,6 @@ <logentry entrytype="feature"> <tags> - <manual type="DB_TRX_ID"/> - <manual type="DB_ROLL_PTR"/> - <manual type="InnoDB"/> - <manual type="DB_MIX_ID"/> - <manual type="errno"/> - <manual type="DB_ROW_ID"/> - </tags> - - <bugs> - <fixes bugid="18934"/> - </bugs> - - <versions> - <version ver="5.0.21"/> - </versions> - - <message> - - <para> - Creating a table in an <literal>InnoDB</literal> database with a - column name that matched the name of an internal - <literal>InnoDB</literal> column (including - <literal>DB_ROW_ID</literal>, <literal>DB_TRX_ID</literal>, - <literal>DB_ROLL_PTR</literal> and <literal>DB_MIX_ID</literal>) - would cause a crash. MySQL now returns error 1005 (cannot create - table) with <literal>errno</literal> set to -1. - </para> - - </message> - - </logentry> - - <logentry entrytype="feature"> - - <tags> <manual type="e"/> <manual type="mysql"/> </tags> @@ -16537,7 +16474,6 @@ </bugs> <versions> - <version ver="5.1.12"/> <version ver="5.1.15"/> </versions> @@ -17729,8 +17665,9 @@ </bugs> <versions> - <version ver="5.1.9"/> <version ver="4.1.19"/> + <version ver="5.0.20"/> + <version ver="5.1.9"/> </versions> <message> @@ -21262,6 +21199,7 @@ </bugs> <versions> + <version ver="5.0.25"/> <version ver="5.1.12"/> </versions> @@ -23661,31 +23599,6 @@ <logentry entrytype="bug"> <tags> - <manual type="REPAIR TABLE"/> - </tags> - - <bugs> - <fixes bugid="17810"/> - </bugs> - - <versions> - <version ver="5.1.10"/> - </versions> - - <message> - - <para> - <literal>REPAIR TABLE</literal> did not restore the length for - packed keys in tables created under MySQL 4.x. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="subqueries"/> </tags> @@ -23694,9 +23607,9 @@ </bugs> <versions> - <version ver="5.1.15"/> - <version ver="5.0.37"/> <version ver="5.0.34"/> + <version ver="5.0.37"/> + <version ver="5.1.15"/> </versions> <message> @@ -24939,7 +24852,7 @@ </logentry> - <logentry entrytype="bug"> + <logentry entrytype="feature"> <tags> <manual type="general_log"/> @@ -24970,14 +24883,14 @@ <listitem> <para> - Truncating mysql.slow_log in a stored procedure after use of - a cursor caused the thread to lock. + Truncating <literal>mysql.slow_log</literal> in a stored + procedure after use of a cursor caused the thread to lock. </para> </listitem> <listitem> <para> - Flushing a log table resulted in warnings. + Flushing a log table resulted in unnecessary warnings. </para> </listitem> @@ -25000,7 +24913,7 @@ </itemizedlist> <para> - The changes provide more well-defined interface characteristics. + The changes provide better-defined interface characteristics. See <xref linkend="log-tables"/>. </para> @@ -27211,34 +27124,6 @@ <logentry entrytype="bug"> <tags> - <highlight type="cluster"/> - <manual type="replication"/> - <manual type="binary log"/> - <manual type="mysqld"/> - </tags> - - <bugs> - <fixes bugid="18472"/> - </bugs> - - <versions> - <version ver="5.1.8"/> - </versions> - - <message> - - <para> - In asynchronous replication scenarios, binary log events could - be lost on the remote <command>mysqld</command>. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="UPGRADE"/> </tags> @@ -33209,24 +33094,27 @@ </tags> <bugs> - <fixes bugid="20769"/> - <fixes bugid="20783"/> <fixes bugid="19022"/> <fixes bugid="20579"/> + <fixes bugid="20769"/> + <fixes bugid="20783"/> + <fixes bugid="20791"/> </bugs> <versions> <version ver="5.0.23"/> + <version ver="5.1.12"/> </versions> <message> <para> - For <command>mysqld</command>, Valgrind revealed problems that - were corrected: A dangling stack pointer being overwritten ; + Valgrind revealed several issues with <command>mysqld</command> + that were corrected: A dangling stack pointer being overwritten; possible uninitialized data in a string comparison; memory corruption in replication slaves when switching databases; - syscall write parameter pointing to uninitialized byte. + <literal>syscall()</literal> write parameter pointing to an + uninitialized byte. </para> </message> @@ -36507,34 +36395,6 @@ <logentry entrytype="bug"> <tags> - <manual type="DOUBLE"/> - <manual type="ORDER BY"/> - </tags> - - <bugs> - <fixes bugid="19690"/> - </bugs> - - <versions> - <version ver="5.0.36"/> - <version ver="5.0.37"/> - <version ver="5.1.16"/> - </versions> - - <message> - - <para> - <literal>ORDER BY</literal> on <literal>DOUBLE</literal> values - could change the set of rows returned by a query. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="SHOW PROFILE"/> </tags> @@ -37444,6 +37304,7 @@ </bugs> <versions> + <version ver="5.0.20"/> <version ver="5.1.8"/> </versions> @@ -37452,7 +37313,7 @@ <para> A <literal>SELECT ... ORDER BY ...</literal> from a view defined using a function could crash the server. An example of such a - view might be <literal>CREATE VIEW v1 AS SELECT SQRT(c1) FROM + view is <literal>CREATE VIEW v1 AS SELECT SQRT(c1) FROM t1</literal>. </para> @@ -37848,6 +37709,8 @@ </bugs> <versions> + <version ver="4.1.19"/> + <version ver="5.0.20"/> <version ver="5.1.8"/> </versions> @@ -39144,23 +39007,54 @@ <logentry entrytype="feature"> + <tags> + <highlight type="packaging"/> + </tags> + <bugs> <fixes bugid="19288"/> </bugs> <versions> + <version ver="4.1.19"/> + <version ver="5.0.21"/> <version ver="5.1.10"/> </versions> - <message> + <message ver="4.1.19"> <para> The + <literal>MySQL-shared-compat-4.1.<replaceable>X</replaceable>-.i386.rpm</literal> + shared compatibility RPMs no longer contain libraries for MySQL + 5.0 and up. They now contain libraries for MySQL 3.23, 4.0, and + 4.1.1 only. + </para> + + </message> + + <message ver="5.0.21"> + + <para> + The + <literal>MySQL-shared-compat-5.0.<replaceable>X</replaceable>-.i386.rpm</literal> + shared compatibility RPMs no longer contain libraries for MySQL + 5.1. This avoids a conflict because the 5.0 and 5.1 libraries + share the same soname number. They now contain libraries for + MySQL 3.23, 4.0, 4.1, and 5.0 only. + </para> + + </message> + + <message ver="5.1.10"> + + <para> + The <literal>MySQL-shared-compat-5.1.<replaceable>X</replaceable>-.i386.rpm</literal> shared compatibility RPMs no longer contain libraries for MySQL 5.0. This avoids a conflict because the 5.0 and 5.1 libraries - share the same soname number. It contains libraries for 3.23, - 4.0, 4.1, and 5.1. + share the same <literal>soname</literal> number. They now + contain libraries for MySQL 3.23, 4.0, 4.1, and 5.1. </para> </message> @@ -39276,27 +39170,6 @@ <logentry entrytype="bug"> - <bugs> - <fixes bugid="19645"/> - </bugs> - - <versions> - <version ver="5.1.15-ndb-6.1.1"/> - </versions> - - <message> - - <para> - When stopping and restarting multiple data nodes, the last node - to be restarted would sometimes hang in Phase 100. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - <tags> <manual type="WITH ROLLUP"/> </tags> @@ -39884,36 +39757,6 @@ </logentry> - <logentry entrytype="bug"> - - <tags> - <manual type="InnoDB"/> - <manual type="transactions"/> - <manual type="HA_ERR_LOCK_TABLE_FULL"/> - <manual type="binary log"/> - </tags> - - <bugs> - <fixes bugid="18283"/> - </bugs> - - <versions> - <version ver="5.0.20"/> - </versions> - - <message> - - <para> - If <literal>InnoDB</literal> encountered a - <literal>HA_ERR_LOCK_TABLE_FULL</literal> error and rolled-back - a transaction, the transaction was still written to the binary - log. - </para> - - </message> - - </logentry> - <logentry entrytype="feature"> <tags> @@ -40342,33 +40185,6 @@ </logentry> - <logentry entrytype="bug"> - - <tags> - <manual type="NUL"/> - </tags> - - <bugs> - <cve ref="CVE-2006-0903"/> - <fixes bugid="17667"/> - </bugs> - - <versions> - <version ver="5.0.23"/> - </versions> - - <message> - - <para> - A <literal>NUL</literal> byte within a comment in a statement - string caused the rest of the string not to be written to the - query log, allowing logging to be bypassed. - </para> - - </message> - - </logentry> - <logentry entrytype="feature"> <tags> @@ -42307,34 +42123,6 @@ </logentry> - <logentry entrytype="bug"> - - <tags> - <highlight type="cluster"/> - <manual type="ndb_config"/> - <manual type="host"/> - </tags> - - <bugs> - <fixes bugid="17582"/> - </bugs> - - <versions> - <version ver="5.0.33"/> - <version ver="5.0.30"/> - </versions> - - <message> - - <para> - The <command>ndb_config</command> utility did not perform host - lookups correctly when using the <option>--host</option> option. - </para> - - </message> - - </logentry> - <logentry entrytype="feature"> <versions> @@ -44706,33 +44494,6 @@ <logentry entrytype="bug"> <tags> - <manual type="TRUNCATE TABLE"/> - <manual type="ALTER TABLE"/> - </tags> - - <bugs> - <fixes bugid="25422"/> - </bugs> - - <versions> - <version ver="5.1.21"/> - </versions> - - <message> - - <para> - The server would hang when performing concurrent <literal>ALTER - TABLE</literal> or <literal>TRUNCATE TABLE</literal> statements - against the log tables. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="Windows"/> </tags> @@ -49216,39 +48977,6 @@ <logentry entrytype="feature"> <tags> - <manual type="load_file"/> - <manual type="LOAD DATA"/> - <manual type="mysql-test-run.pl"/> - <manual type="mysqltest"/> - <manual type="secure-file-priv"/> - </tags> - - <bugs> - <fixes bugid="18628"/> - </bugs> - - <versions> - <version ver="5.0.41"/> - </versions> - - <message> - - <para> - Added the <option>--secure-file-priv</option> option for - <command>mysql-test-run.pl</command>, which limits the effect of - the <literal>load_file</literal> command for - <command>mysqltest</command> and for the <literal>LOAD - DATA</literal> and <literal>SELECT ... INTO OUTFILE</literal> - statements to work with files in a given directory. - </para> - - </message> - - </logentry> - - <logentry entrytype="feature"> - - <tags> <highlight type="cluster"/> <manual type="cluster"/> <manual type="ndb_mgmd"/> @@ -51132,31 +50860,6 @@ </logentry> - <logentry entrytype="feature"> - - <bugs> - <fixes bugid="19288"/> - </bugs> - - <versions> - <version ver="5.0.21"/> - </versions> - - <message> - - <para> - The - <literal>MySQL-shared-compat-5.0.<replaceable>X</replaceable>-.i386.rpm</literal> - shared compatibility RPMs no longer contain libraries for MySQL - 5.1. This avoids a conflict because the 5.0 and 5.1 libraries - share the same soname number. It contains libraries for 3.23, - 4.0, 4.1, and 5.0. - </para> - - </message> - - </logentry> - <logentry entrytype="bug"> <tags> @@ -53050,15 +52753,34 @@ <bugs> <fixes bugid="21789"/> + <seealsobug bugid="25301"/> </bugs> <versions> - <version ver="5.1.15"/> <version ver="4.1.23"/> <version ver="5.0.32"/> <version ver="5.0.33"/> + <version ver="5.1.15"/> </versions> + <message ver="4.1.23"> + + <para> + It was possible to use <literal>DATETIME</literal> values whose + year, month, and day parts were all zeroes but whose hour, + minute, and second parts contained nonzero values, an example of + such an illegal <literal>DATETIME</literal> being + <literal>'0000-00-00 11:23:45'</literal>. + </para> + + <note> + <para> + This fix was reverted in MySQL 4.1.24. + </para> + </note> + + </message> + <message> <para> @@ -53069,10 +52791,30 @@ <literal>'0000-00-00 11:23:45'</literal>. </para> + <note> + <para> + This fix was reverted in MySQL 5.0.40. + </para> + </note> + + </message> + + <message ver="5.1.15"> + <para> - This patch was reverted in MySQL 5.1.18. + It was possible to use <literal>DATETIME</literal> values whose + year, month, and day parts were all zeroes but whose hour, + minute, and second parts contained nonzero values, an example of + such an illegal <literal>DATETIME</literal> being + <literal>'0000-00-00 11:23:45'</literal>. </para> + <note> + <para> + This fix was reverted in MySQL 5.1.18. + </para> + </note> + </message> </logentry> @@ -55589,32 +55331,6 @@ <logentry entrytype="bug"> <tags> - <manual type="general_log"/> - </tags> - - <bugs> - <fixes bugid="29129"/> - </bugs> - - <versions> - <version ver="5.1.21"/> - </versions> - - <message> - - <para> - Changing the value of the <literal>general_log</literal> system - variable while a global read lock was in place resulted in - deadlock. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="collation"/> </tags> @@ -56247,6 +55963,7 @@ </bugs> <versions> + <version ver="5.0.23"/> <version ver="5.1.11"/> </versions> @@ -56689,13 +56406,15 @@ </bugs> <versions> + <version ver="4.1.21"/> <version ver="5.0.23"/> + <version ver="5.1.12"/> </versions> <message> <para> - <literal>InnoDB</literal> did not increment the + <literal>InnoDB</literal> failed to increment the <literal>handler_read_prev</literal> counter. </para> @@ -56877,15 +56596,17 @@ </bugs> <versions> - <version ver="5.1.12"/> + <version ver="4.1.22"/> <version ver="5.0.24"/> + <version ver="5.1.12"/> </versions> <message> <para> - Using the extended syntax for <literal>TRIM()</literal> — - that is, <literal>TRIM(... FROM ...)</literal> — in a + Using the extended syntax for + <function role="sql">TRIM()</function> — that is, + <literal>TRIM(... FROM ...)</literal> — in a <literal>SELECT</literal> statement defining a view caused an invalid syntax error when selecting from the view. </para> @@ -58892,14 +58613,15 @@ <bugs> <fixes bugid="19370"/> + <seealsobug bugid="25301"/> </bugs> <versions> - <version ver="5.1.12"/> <version ver="5.0.25"/> + <version ver="5.1.12"/> </versions> - <message> + <message ver="5.0.25"> <para> When not running in strict mode, the server failed to convert @@ -58908,10 +58630,29 @@ when inserting it into a table. </para> + <note> + <para> + This fix was reverted in MySQL 5.0.40. + </para> + </note> + + </message> + + <message ver="5.1.12"> + <para> - This patch was reverted in MySQL 5.1.18. + When not running in strict mode, the server failed to convert + the invalid years portion of a <literal>DATE</literal> or + <literal>DATETIME</literal> value to <literal>'0000'</literal> + when inserting it into a table. </para> + <note> + <para> + This fix was reverted in MySQL 5.1.18. + </para> + </note> + </message> </logentry> @@ -62200,10 +61941,10 @@ </bugs> <versions> + <version ver="4.1.23"/> + <version ver="5.0.32"/> <version ver="5.0.33"/> <version ver="5.1.15"/> - <version ver="5.0.32"/> - <version ver="4.1.23"/> </versions> <message> @@ -63883,35 +63624,7 @@ <logentry entrytype="bug"> <tags> - <manual type="FROM"/> - <manual type="subqueries"/> - <manual type="binary log"/> - </tags> - - <bugs> - <fixes bugid="19136"/> - </bugs> - - <versions> - <version ver="4.1.21"/> - <version ver="5.0.23"/> - </versions> - - <message> - - <para> - Use of uninitialized user variables in a subquery in the - <literal>FROM</literal> clause results in bad entries in the - binary log. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> + <highlight type="replication"/> <manual type="replication"/> <manual type="MyISAM"/> <manual type="binary log"/> @@ -63928,15 +63641,11 @@ <message> <para> - Replication: sometimes the master gets a non-fatal error during - the execution of a statement but finally the statements succeeds - (for example, a write to a <literal>MyISAM</literal> table first - receives "no space left on device" but is able to - finally complete, see <xref linkend="full-disk"/>); the bug was - that the master forgot to reset the error code to 0 after - success, so the error code got into its binary log, thus making - the slave giving false alarms like "did not get the same - error as on master". + Following a non-fatal error during the execution of a statement + that later succeeded, the master failed to reset the error code + to 0, so the error code was written into the binary log. This + caused false <errortext>Did not get the same error as on + master</errortext> errors on the slave. </para> </message> @@ -65049,6 +64758,7 @@ <logentry entrytype="bug"> <tags> + <highlight type="securityfix"/> <manual type="NUL"/> </tags> @@ -65058,6 +64768,7 @@ </bugs> <versions> + <version ver="5.0.23"/> <version ver="5.1.10"/> </versions> @@ -67968,34 +67679,6 @@ <logentry entrytype="bug"> <tags> - <highlight type="diskdata"/> - <manual type="cluster"/> - </tags> - - <bugs> - <fixes bugid="17605"/> - </bugs> - - <versions> - <version ver="5.1.14-ndb-6.1.0"/> - </versions> - - <message> - - <para> - Extents that should have been available for re-use following a - <literal>DROP TABLE</literal> operation were not actually made - available again until after the cluster had performed a local - checkpoint. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="UPDATE"/> </tags> @@ -75478,32 +75161,6 @@ </logentry> - <logentry entrytype="feature"> - - <tags> - <manual type="replication"/> - <manual type="CREATE FUNCTION"/> - </tags> - - <bugs> - <fixes bugid="17671"/> - </bugs> - - <versions> - <version ver="5.1.18"/> - </versions> - - <message> - - <para> - <literal>CREATE FUNCTION</literal> statements and their effects - were not replicated correctly. - </para> - - </message> - - </logentry> - <logentry entrytype="bug"> <tags> @@ -76131,47 +75788,6 @@ </logentry> - <logentry entrytype="feature"> - - <tags> - <manual type="TYPE"/> - </tags> - - <bugs> - <fixes bugid="17501"/> - </bugs> - - <versions> - <version ver="5.1.8"/> - </versions> - - <message> - - <para> - In order not to break legacy applications, support for - <literal>TYPE = <replaceable>engine_name</replaceable> - </literal> has been restored, but now generates a warning. - </para> - - <important> - <para> - This option has been deprecated since MySQL 4.0. - <emphasis>Beginning with MySQL 5.2, <literal>TYPE = - <replaceable>engine_name</replaceable> </literal> will no - longer be available and will produce a syntax - error</emphasis>. <emphasis>You should not use - <literal>TYPE</literal> in any new applications, and you - should immediately begin conversion of existing applications - to use the <literal>ENGINE = - <replaceable>engine_name</replaceable> </literal> syntax - instead</emphasis>. - </para> - </important> - - </message> - - </logentry> - <logentry entrytype="bug"> <tags> @@ -77135,33 +76751,6 @@ <logentry entrytype="bug"> <tags> - <manual type="mysql"/> - <manual type="triggers"/> - </tags> - - <bugs> - <fixes bugid="18361"/> - </bugs> - - <versions> - <version ver="5.0.25"/> - </versions> - - <message> - - <para> - Triggers on tables in the <literal>mysql</literal> database - caused a server crash. Triggers for tables in this database now - are disallowed. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <highlight type="cluster"/> <manual type="ALTER TABLESPACE"/> </tags> @@ -77773,7 +77362,7 @@ <para> Takeover for local checkpointing due to multiple failures of - master nodes was sometimes incorrect handled. + master nodes was sometimes incorrectly handled. </para> </message> @@ -77911,9 +77500,38 @@ <para> The deprecated items shown in the table are not guaranteed to be - available in MySQL 5.2 or later. + available in MySQL 6.0 or later. </para> + <important> + <formalpara> + + <title><literal>TYPE</literal> vs <literal>ENGINE</literal> + + </title> + <para> + In order not to break legacy applications, support for + <literal>TYPE = <replaceable>engine_name</replaceable> + </literal> — deprecated since MySQL 4.0 — has + been restored, but now generates a warning. + </para> + + </formalpara> + <para> + <emphasis>Beginning with MySQL 6.0, <literal>TYPE = + <replaceable>engine_name</replaceable> </literal> will no + longer be available and will produce a syntax + error</emphasis>. + </para> + <para> + <emphasis>You should not use <literal>TYPE</literal> in any + new applications, and you should immediately begin conversion + of existing applications to use the <literal>ENGINE = + <replaceable>engine_name</replaceable> </literal> syntax + instead</emphasis>. + </para> + </important> + </message> </logentry> @@ -84440,35 +84058,6 @@ </logentry> - <logentry entrytype="bug"> - - <tags> - <highlight type="cluster"/> - <manual type="cluster"/> - </tags> - - <bugs> - <fixes bugid="18298"/> - </bugs> - - <versions> - <version ver="4.1.19"/> - <version ver="5.0.20"/> - </versions> - - <message> - - <para> - The cluster created a crashed replica of a table having an - ordered index — or when logging was not enabled, of a - table having a table or unique index — leading to a crash - of the cluster following 8 successive restarts. - </para> - - </message> - - </logentry> - <logentry entrytype="feature"> <tags> @@ -85004,6 +84593,7 @@ <versions> <version ver="4.1.19"/> <version ver="5.0.20"/> + <version ver="5.1.8"/> </versions> <message> @@ -86444,35 +86034,6 @@ <logentry entrytype="bug"> <tags> - <highlight type="cluster"/> - <manual type="cluster"/> - </tags> - - <bugs> - <fixes bugid="18676"/> - </bugs> - - <versions> - <version ver="5.1.18-ndb-6.2.1"/> - </versions> - - <message> - - <para> - When trying to create tables on an SQL node not connected to the - cluster, a misleading error message <errortext>Table - '<replaceable>tbl_name</replaceable>' already exists</errortext> - was generated. The error now generated is <errortext>Could not - connect to storage engine</errortext>. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="GET_LL"/> </tags> @@ -87756,8 +87317,9 @@ </bugs> <versions> - <version ver="5.1.17"/> <version ver="5.0.38"/> + <version ver="5.0.41"/> + <version ver="5.1.17"/> </versions> <message> @@ -87765,9 +87327,10 @@ <para> Added the <option>--secure-file-priv</option> option for <command>mysqld</command>, which limits the effect of the - <literal>LOAD_FILE()</literal> function and the <literal>LOAD - DATA</literal> and <literal>SELECT ... INTO OUTFILE</literal> - statements to work only with files in a given directory. + <function role="sql">LOAD_FILE()</function> function and the + <literal>LOAD DATA</literal> and <literal>SELECT ... INTO + OUTFILE</literal> statements to work only with files in a given + directory. </para> </message> @@ -90817,32 +90380,6 @@ </logentry> - <logentry entrytype="bug"> - - <tags> - <manual type="mysql_upgrade"/> - </tags> - - <bugs> - <fixes bugid="20403"/> - <fixes bugid="18516"/> - </bugs> - - <versions> - <version ver="5.0.23"/> - </versions> - - <message> - - <para> - <command>mysql_upgrade</command> was missing from binary MySQL - distributions. - </para> - - </message> - - </logentry> - <logentry entrytype="feature"> <tags> @@ -91754,29 +91291,6 @@ <logentry entrytype="feature"> <bugs> - <fixes bugid="19288"/> - </bugs> - - <versions> - <version ver="4.1.19"/> - </versions> - - <message> - - <para> - The - <literal>MySQL-shared-compat-4.1.<replaceable>X</replaceable>-.i386.rpm</literal> - shared compatibility RPMs no longer contain libraries for MySQL - 5.0 and up. It contains libraries for 3.23, 4.0, and 4.1.1. - </para> - - </message> - - </logentry> - - <logentry entrytype="feature"> - - <bugs> <fixes bugid="30625"/> </bugs> @@ -92825,6 +92339,8 @@ <versions> <version ver="4.1.19"/> + <version ver="5.0.21"/> + <version ver="5.1.10"/> </versions> <message> @@ -93485,32 +93001,6 @@ </logentry> - <logentry entrytype="feature"> - - <tags> - <manual type="replication"/> - </tags> - - <bugs> - <fixes bugid="20384"/> - </bugs> - - <versions> - <version ver="5.1.18"/> - </versions> - - <message> - - <para> - Effects of scheduled events on a replication master were both - replicated and executed on the slave, causing double execution - of events. - </para> - - </message> - - </logentry> - <logentry entrytype="bug"> <tags> @@ -93621,6 +93111,7 @@ </bugs> <versions> + <version ver="5.0.23"/> <version ver="5.1.12"/> </versions> @@ -95743,32 +95234,6 @@ <logentry entrytype="bug"> <tags> - <manual type="handler_read_prev"/> - </tags> - - <bugs> - <fixes bugid="19542"/> - </bugs> - - <versions> - <version ver="5.1.12"/> - <version ver="4.1.21"/> - </versions> - - <message> - - <para> - InnoDB did not increment the - <literal>handler_read_prev</literal> counter. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="stored procedure"/> </tags> @@ -107289,6 +106754,7 @@ </bugs> <versions> + <version ver="5.1.14-ndb-6.1.0"/> <version ver="5.1.15"/> </versions> @@ -107297,7 +106763,7 @@ <para> Extents that should have been available for re-use following a <literal>DROP TABLE</literal> operation were not actually made - available again until after the cluster performed a local + available again until after the cluster had performed a local checkpoint. </para> @@ -109279,43 +108745,6 @@ <logentry entrytype="feature"> <tags> - <manual type="SSL"/> - <manual type="ssl-verify-server-cert"/> - <manual type="mysql_options()"/> - <manual type="MYSQL_OPT_SSL_VERIFY_SERVER_CERT"/> - </tags> - - <bugs> - <fixes bugid="17208"/> - </bugs> - - <versions> - <version ver="5.0.23"/> - </versions> - - <message> - - <para> - Added the <option>--ssl-verify-server-cert</option> option to - MySQL client programs. This option causes the server's Common - Name value in the certificate that the server sends to the - client to be verified against the hostname that the client uses - for connecting to the server, and the connection is rejected if - there is a mismatch. Added - <literal>MYSQL_OPT_SSL_VERIFY_SERVER_CERT</literal> option for - the <function role="capi">mysql_options()</function> C API - function to enable this verification. This feature can be used - to prevent man-in-the-middle attacks. Verification is disabled - by default. - </para> - - </message> - - </logentry> - - <logentry entrytype="feature"> - - <tags> <manual type="LIMIT"/> </tags> @@ -109569,34 +108998,6 @@ <logentry entrytype="bug"> <tags> - <manual type="NULL"/> - <manual type="IS NULL"/> - <manual type="IN"/> - </tags> - - <bugs> - <fixes bugid="17047"/> - </bugs> - - <versions> - <version ver="4.1.23"/> - </versions> - - <message> - - <para> - <literal>IN()</literal> can return <literal>NULL</literal>, but - did not signal that to the query processor, causing incorrect - results for <literal>IS NULL</literal> operations. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="InnoDB"/> </tags> @@ -111384,28 +110785,6 @@ <logentry entrytype="bug"> - <bugs> - <fixes bugid="18912"/> - </bugs> - - <versions> - <version ver="5.1.10"/> - <version ver="5.0.21"/> - </versions> - - <message> - - <para> - MySQL would not compile on Linux distributions that use the - tinfo library. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - <tags> <manual type="triggers"/> </tags> @@ -111703,29 +111082,6 @@ <logentry entrytype="bug"> - <bugs> - <fixes bugid="18386"/> - </bugs> - - <versions> - <version ver="5.0.20"/> - </versions> - - <message> - - <para> - A <literal>SELECT ... ORDER BY ...</literal> from a view defined - using a function could crash the server. An example of such a - view might be <literal>CREATE VIEW AS SELECT SQRT(c1) FROM - t1</literal>. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - <tags> <manual type="BIT"/> <manual type="MERGE"/> @@ -112227,8 +111583,9 @@ </bugs> <versions> - <version ver="5.0.33"/> + <version ver="4.1.23"/> <version ver="5.0.32"/> + <version ver="5.0.33"/> <version ver="5.1.14"/> </versions> @@ -113068,14 +112425,17 @@ <versions> <version ver="4.1.23"/> + <version ver="5.0.36"/> + <version ver="5.0.37"/> + <version ver="5.1.16"/> </versions> <message> <para> - <literal>ORDER BY</literal> on <literal>DOUBLE</literal> or - <literal>DECIMAL</literal> values could change the set of rows - returned by a query. + <literal>ORDER BY</literal> values of the + <literal>DOUBLE</literal> or <literal>DECIMAL</literal> types + could change the result returned by a query. </para> </message> @@ -113441,30 +112801,6 @@ <logentry entrytype="bug"> - <bugs> - <fixes bugid="16861"/> - </bugs> - - <versions> - <version ver="5.1.15"/> - <version ver="5.0.37"/> - <version ver="5.0.34"/> - </versions> - - <message> - - <para> - A user-defined variable could be assigned an incorrect value if - a temporary table was employed in obtaining the result of the - query used to determine its value. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - <tags> <manual type="MyISAM"/> <manual type="make_win_bin_dist"/> @@ -117134,39 +116470,6 @@ <logentry entrytype="bug"> <tags> - <highlight type="cluster"/> - <manual type="cluster"/> - <manual type="CREATE TABLE"/> - </tags> - - <bugs> - <fixes bugid="18385"/> - </bugs> - - <versions> - <version ver="5.1.8"/> - </versions> - - <message> - - <para> - A node restart immediately following a <literal>CREATE - TABLE</literal> would fail. - </para> - - <important> - <para> - This fix supports 2-node Clusters only. - </para> - </important> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="LAST_INSERT_ID"/> </tags> @@ -117342,41 +116645,7 @@ <logentry entrytype="bug"> - <tags> - <manual type="replication"/> - <manual type="InnoDB"/> - <manual type="mysqld"/> - </tags> - <bugs> - <fixes bugid="20783"/> - <fixes bugid="19022"/> - <fixes bugid="20579"/> - <fixes bugid="20791"/> - </bugs> - - <versions> - <version ver="5.1.12"/> - </versions> - - <message> - - <para> - For <command>mysqld</command>, Valgrind revealed problems that - were corrected: Possible uninitialized data in a string - comparison ; memory corruption in replication slaves when - switching databases; syscall write parameter pointing to - uninitialized byte; uninitialized doublewrite memory in - <literal>InnoDB</literal>. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <bugs> <fixes bugid="1946"/> </bugs> @@ -117869,31 +117138,6 @@ </logentry> - <logentry entrytype="bug"> - - <tags> - <manual type="stored procedure"/> - </tags> - - <bugs> - <fixes bugid="17876"/> - </bugs> - - <versions> - <version ver="5.1.21"/> - </versions> - - <message> - - <para> - Truncating mysql.slow_log in a stored procedure after use of a - cursor caused the thread to lock. - </para> - - </message> - - </logentry> - <logentry entrytype="feature"> <tags> @@ -123567,7 +122811,7 @@ </logentry> - <logentry entrytype="feature"> + <logentry entrytype="bug"> <tags> <manual type="DB_TRX_ID"/> @@ -123583,18 +122827,21 @@ <versions> <version ver="4.1.19"/> + <version ver="5.0.21"/> <version ver="5.1.10"/> </versions> <message> <para> - Creating a table in an InnoDB database with a column name that - matched the name of an internal InnoDB column (including + Creating a table in an <literal>InnoDB</literal> database with a + column name that matched the name of an internal + <literal>InnoDB</literal> column (including <literal>DB_ROW_ID</literal>, <literal>DB_TRX_ID</literal>, <literal>DB_ROLL_PTR</literal> and <literal>DB_MIX_ID</literal>) - would cause a crash. MySQL now returns error 1005 (cannot create - table) with <literal>errno</literal> set to -1. + would cause a crash. MySQL now returns Error 1005 + <errortext>Cannot create table</errortext> with + <literal>errno</literal> set to -1. </para> </message> @@ -123995,41 +123242,6 @@ <logentry entrytype="bug"> <tags> - <manual type="DATE_SUB"/> - <manual type="NULL"/> - <manual type="DATE_ADD"/> - </tags> - - <bugs> - <fixes bugid="18997"/> - </bugs> - - <versions> - <version ver="5.1.11"/> - </versions> - - <message> - - <para> - For dates with 4-digit year parts less than 200, an implicit - conversion to add a century was applied for date arithmetic - performed with <literal>DATE_ADD()</literal>, - <literal>DATE_SUB()</literal>, <literal>+ INTERVAL</literal>, - and <literal>- INTERVAL</literal>. (For example, - <literal>DATE_ADD('0050-01-01 00:00:00', INTERVAL 0 - SECOND)</literal> became <literal>'2050-01-01 - 00:00:00'</literal>.) Now these operations return - <literal>NULL</literal> rather than an incorrect - non-<literal>NULL</literal> value. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="VARCHAR"/> </tags> @@ -124243,6 +123455,7 @@ <tags> <manual type="DATE_SUB"/> <manual type="DATE_ADD"/> + <manual type="INTERVAL"/> </tags> <bugs> @@ -124252,6 +123465,7 @@ <versions> <version ver="5.0.45"/> <version ver="5.0.44"/> + <version ver="5.1.11"/> <version ver="5.1.19"/> </versions> @@ -124270,6 +123484,23 @@ </message> + <message ver="5.1.11"> + + <para> + For dates with 4-digit year parts less than 200, an implicit + conversion to add a century was applied for date arithmetic + performed with <literal>DATE_ADD()</literal>, + <literal>DATE_SUB()</literal>, <literal>+ INTERVAL</literal>, + and <literal>- INTERVAL</literal>. (For example, + <literal>DATE_ADD('0050-01-01 00:00:00', INTERVAL 0 + SECOND)</literal> became <literal>'2050-01-01 + 00:00:00'</literal>.) Now these operations return + <literal>NULL</literal> rather than an incorrect + non-<literal>NULL</literal> value. + </para> + + </message> + </logentry> <logentry entrytype="bug"> @@ -128359,6 +127590,8 @@ </bugs> <versions> + <version ver="4.1.21"/> + <version ver="5.0.23"/> <version ver="5.1.11"/> </versions> @@ -128366,8 +127599,8 @@ <para> Use of uninitialized user variables in a subquery in the - <literal>FROM</literal> clause resulted in bad entries in the - binary log. + <literal>FROM</literal> clause resulted in invalid entries in + the binary log. </para> </message> @@ -129221,6 +128454,7 @@ <versions> <version ver="5.0.23"/> + <version ver="5.1.10"/> </versions> <message> @@ -135839,26 +135073,6 @@ </logentry> - <logentry entrytype="bug"> - - <bugs> - <fixes bugid="23044"/> - </bugs> - - <versions> - <version ver="5.1.21"/> - </versions> - - <message> - - <para> - Flushing a log table resulted in warnings. - </para> - - </message> - - </logentry> - <logentry entrytype="feature"> <tags>
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r8570 - trunk/dynamic-docs/changelog | jon | 7 Nov |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.885 sec. using MySQL 5.1.14-beta-log