| List: | Internals | « Previous MessageNext Message » | |
| From: | paul | Date: | July 22 2005 11:51pm |
| Subject: | bk commit - mysqldoc@docsrva tree (paul:1.3105) | ||
| View as plain text | |||
Below is the list of changes that have just been committed into a local mysqldoc repository of paul. When paul does a push these changes will be propagated to the main repository and, within 24 hours after the push, to the public repository. For information on how to access the public repository see http://www.mysql.com/doc/I/n/Installing_source_tree.html ChangeSet 1.3105 05/07/22 16:51:04 paul@stripped +3 -0 Fix some news item problems. refman/news.xml 1.94 05/07/22 16:51:02 paul@stripped +71 -70 Reformat. refman-5.0/news.xml 1.79 05/07/22 16:51:01 paul@stripped +46 -45 Fix invalid tags (probably bad merge), fix URL, reformat. refman-4.1/news.xml 1.65 05/07/22 16:51:00 paul@stripped +25 -24 Fix URL, reformat. # This is a BitKeeper patch. What follows are the unified diffs for the # set of deltas contained in the patch. The rest of the patch, the part # that BitKeeper cares about, is below these diffs. # User: paul # Host: frost.snake.net # Root: /Volumes/frost2/MySQL/bk/mysqldoc --- 1.64/refman-4.1/news.xml 2005-07-22 10:44:40 -05:00 +++ 1.65/refman-4.1/news.xml 2005-07-22 16:51:00 -05:00 @@ -217,17 +217,17 @@ </para> <itemizedlist> - + <listitem> <para> - <literal>MySQL Cluster</literal>: A new + <literal>MySQL Cluster</literal>: A new <literal>-p</literal> option is available for use with the - <command>ndb_mgmd</command> client. When called with this - option, <command>ndb_mgmd</command> prints all configuration + <command>ndb_mgmd</command> client. When called with this + option, <command>ndb_mgmd</command> prints all configuration data to <literal>stdout</literal>, then exits. </para> </listitem> - + </itemizedlist> <para> @@ -238,28 +238,28 @@ describe the issue that was fixed. Use past tense. --> <itemizedlist> - + <listitem> <para> - The C API function - <literal>mysql_statement_reset()</literal> did not clear + The C API function + <literal>mysql_statement_reset()</literal> did not clear error information. (Bug #11183) </para> </listitem> - + <listitem> <para> - Multiple-table <literal>UPDATE</literal> queries using - <literal>CONVERT_TZ()</literal> would fail with an error. + Multiple-table <literal>UPDATE</literal> queries using + <literal>CONVERT_TZ()</literal> would fail with an error. (Bug #9979) </para> </listitem> - + <listitem> <para> - <literal>mysql_fetch_fields()</literal> returned incorrect - length information for <literal>MEDIUM</literal> and - <literal>LONG</literal> <literal>TEXT</literal> and + <literal>mysql_fetch_fields()</literal> returned incorrect + length information for <literal>MEDIUM</literal> and + <literal>LONG</literal> <literal>TEXT</literal> and <literal>BLOB</literal> columns. (Bug #9735) </para> </listitem> @@ -365,7 +365,7 @@ Security improvement: Applied a patch that addresses a <literal>zlib</literal> data vulnerability that could result in a buffer overflow and code execution. - (<ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-0711">CAN-2005-2096</ulink>) + (<ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-2096">CAN-2005-2096</ulink>) (Bug #11844) </para> </listitem> @@ -470,10 +470,10 @@ describe the issue that was fixed. Use past tense. --> <itemizedlist> - + <listitem> <para> - When used within a subquery, <literal>SUBSTRING()</literal> + When used within a subquery, <literal>SUBSTRING()</literal> returned an empty string. (Bug #10269) </para> </listitem> @@ -3177,9 +3177,10 @@ <listitem> <para> - InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, - single table <literal>UPDATE…SELECT</literal> and single - table <literal>DELETE…SELECT</literal> clauses when + InnoDB: Relaxed locking in + <literal>INSERT…SELECT</literal>, single table + <literal>UPDATE…SELECT</literal> and single table + <literal>DELETE…SELECT</literal> clauses when <literal>innodb_locks_unsafe_for_binlog</literal> is used and isolation level of the transaction is not serializable. <literal>InnoDB</literal> uses consistent read in these @@ -26848,9 +26849,9 @@ <para> Changed <literal>LIKE</literal> character comparison to behave as <literal>=</literal>; This means that <literal>'e' - LIKE 'é'</literal> is now true. (If the line doesn't display - correctly, the latter 'e' is a French 'e' with an acute - accent above.) + LIKE 'é'</literal> is now true. (If the line doesn't + display correctly, the latter 'e' is a French 'e' with an + acute accent above.) </para> </listitem> --- 1.78/refman-5.0/news.xml 2005-07-22 10:40:56 -05:00 +++ 1.79/refman-5.0/news.xml 2005-07-22 16:51:01 -05:00 @@ -246,38 +246,37 @@ Security improvement: Applied a patch that addresses a <literal>zlib</literal> data vulnerability that could result in a buffer overflow and code execution. - (<ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-0711">CAN-2005-2096</ulink>) + (<ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-2096">CAN-2005-2096</ulink>) (Bug #11844) </para> </listitem> - + <listitem> <para> - The viewing of triggers and trigger metadata has been + The viewing of triggers and trigger metadata has been enhanced as follows: - + <itemizedlist> - + <listitem> <para> - An extension to the <literal>SHOW</literal> command - has been added: <literal>SHOW TRIGGERS</literal> can - be used to view a listing of triggers. See + An extension to the <literal>SHOW</literal> command + has been added: <literal>SHOW TRIGGERS</literal> can + be used to view a listing of triggers. See <xref linkend="show-triggers"/> for details. </para> </listitem> - + <listitem> <para> - The <literal>INFORMATION_SCHEMA</literal> database now - includes a <literal>TRIGGERS</literal> table. See - <xref linkend="triggers-table"/> for details. (Bug + The <literal>INFORMATION_SCHEMA</literal> database now + includes a <literal>TRIGGERS</literal> table. See + <xref linkend="triggers-table"/> for details. (Bug #9586) </para> </listitem> - + </itemizedlist> - </para> </listitem> @@ -304,13 +303,13 @@ (Bug #9581, Bug #8406) </para> </listitem> - + <listitem> <para> - <literal>MySQL Cluster</literal>: A new + <literal>MySQL Cluster</literal>: A new <literal>-p</literal> option is available for use with the - <command>ndb_mgmd</command> client. When called with this - option, <command>ndb_mgmd</command> prints all configuration + <command>ndb_mgmd</command> client. When called with this + option, <command>ndb_mgmd</command> prints all configuration data to <literal>stdout</literal>, then exits. </para> </listitem> @@ -338,60 +337,60 @@ </para> <itemizedlist> - + <listitem> <para> - The C API function - <literal>mysql_statement_reset()</literal> did not clear + The C API function + <literal>mysql_statement_reset()</literal> did not clear error information. (Bug #11183) </para> </listitem> - + <listitem> <para> - On Windows, the search path used by MySQL applications for - <filename>my.ini</filename> now includes - <filename>..\my.ini</filename> (that is, the application's + On Windows, the search path used by MySQL applications for + <filename>my.ini</filename> now includes + <filename>..\my.ini</filename> (that is, the application's parent directory, and hence, the installation directory). (Bug #10419) </para> </listitem> - + <listitem> <para> - When used within a subquery, <literal>SUBSTRING()</literal> + When used within a subquery, <literal>SUBSTRING()</literal> returned an empty string. (Bug #10269) </para> </listitem> - + <listitem> <para> - Multiple-table <literal>UPDATE</literal> queries using - <literal>CONVERT_TZ()</literal> would fail with an error. + Multiple-table <literal>UPDATE</literal> queries using + <literal>CONVERT_TZ()</literal> would fail with an error. (Bug #9979) </para> </listitem> - + <listitem> <para> - <literal>mysql_fetch_fields()</literal> returned incorrect - length information for <literal>MEDIUM</literal> and - <literal>LONG</literal> <literal>TEXT</literal> and + <literal>mysql_fetch_fields()</literal> returned incorrect + length information for <literal>MEDIUM</literal> and + <literal>LONG</literal> <literal>TEXT</literal> and <literal>BLOB</literal> columns. (Bug #9735) </para> </listitem> - + <listitem> <para> - <literal>mysqlbinlog</literal> was failing the test suite - on Windows due to <literal>BOOL</literal> being incorrectly + <literal>mysqlbinlog</literal> was failing the test suite on + Windows due to <literal>BOOL</literal> being incorrectly cast to <literal>INT</literal>. (Bug #11567) </para> </listitem> - + <listitem> <para> - <literal>NDBCLuster</literal>: Server left core files + <literal>NDBCLuster</literal>: Server left core files following shutdown if data nodes had failed. (Bug #11516) </para> </listitem> @@ -451,9 +450,11 @@ <para> Server had access denied errors for default accounts on machines where 127.0.0.1 != 'localhost'. (Bug #11822) - </para> - </listitem> + </para> + </listitem> + <listitem> + <para> For several character sets, MySQL incorrectly converted the character code for the division sign to the <literal>eucjpms</literal> character set. (Bug #11717) @@ -464,7 +465,6 @@ <para> When invoked within a view, <literal>SUBTIME()</literal> returned incorrect values. (Bug #11760) ->>>>>>> </para> </listitem> @@ -4442,9 +4442,10 @@ <listitem> <para> - InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, - single table <literal>UPDATE…SELECT</literal> and single - table <literal>DELETE…SELECT</literal> clauses when + InnoDB: Relaxed locking in + <literal>INSERT…SELECT</literal>, single table + <literal>UPDATE…SELECT</literal> and single table + <literal>DELETE…SELECT</literal> clauses when <literal>innodb_locks_unsafe_for_binlog</literal> is used and isolation level of the transaction is not serializable. <literal>InnoDB</literal> uses consistent read in these --- 1.93/refman/news.xml 2005-07-22 10:40:56 -05:00 +++ 1.94/refman/news.xml 2005-07-22 16:51:02 -05:00 @@ -243,48 +243,46 @@ (Bug #11844) </para> </listitem> - + <listitem> <para> - The viewing of triggers and trigger metadata has been + The viewing of triggers and trigger metadata has been enhanced as follows: - + <itemizedlist> - + <listitem> <para> - An extension to the <literal>SHOW</literal> command - has been added: <literal>SHOW TRIGGERS</literal> can - be used to view a listing of triggers. See + An extension to the <literal>SHOW</literal> command + has been added: <literal>SHOW TRIGGERS</literal> can + be used to view a listing of triggers. See <xref linkend="show-triggers"/> for details. </para> </listitem> - + <listitem> <para> - The <literal>INFORMATION_SCHEMA</literal> database now - includes a <literal>TRIGGERS</literal> table. See - <xref linkend="triggers-table"/> for details. (Bug + The <literal>INFORMATION_SCHEMA</literal> database now + includes a <literal>TRIGGERS</literal> table. See + <xref linkend="triggers-table"/> for details. (Bug #9586) </para> </listitem> - + </itemizedlist> - </para> </listitem> - + <listitem> <para> - On Windows, the search path used by MySQL applications for - <filename>my.ini</filename> now includes - <filename>..\my.ini</filename> (that is, the application's + On Windows, the search path used by MySQL applications for + <filename>my.ini</filename> now includes + <filename>..\my.ini</filename> (that is, the application's parent directory, and hence, the installation directory). (Bug #10419) </para> </listitem> - <listitem> <para> Added <literal>mysql_get_character_set_info()</literal> C @@ -308,13 +306,13 @@ (Bug #9581, Bug #8406) </para> </listitem> - + <listitem> <para> - <literal>MySQL Cluster</literal>: A new + <literal>MySQL Cluster</literal>: A new <literal>-p</literal> option is available for use with the - <command>ndb_mgmd</command> client. When called with this - option, <command>ndb_mgmd</command> prints all configuration + <command>ndb_mgmd</command> client. When called with this + option, <command>ndb_mgmd</command> prints all configuration data to <literal>stdout</literal>, then exits. </para> </listitem> @@ -342,50 +340,50 @@ </para> <itemizedlist> - + <listitem> <para> - The C API function - <literal>mysql_statement_reset()</literal> did not clear + The C API function + <literal>mysql_statement_reset()</literal> did not clear error information. (Bug #11183) </para> </listitem> - + <listitem> <para> - When used within a subquery, <literal>SUBSTRING()</literal> + When used within a subquery, <literal>SUBSTRING()</literal> returned an empty string. (Bug #10269) </para> </listitem> - + <listitem> <para> - Multiple-table <literal>UPDATE</literal> queries using - <literal>CONVERT_TZ()</literal> would fail with an error. + Multiple-table <literal>UPDATE</literal> queries using + <literal>CONVERT_TZ()</literal> would fail with an error. (Bug #9979) </para> </listitem> - + <listitem> <para> - <literal>mysql_fetch_fields()</literal> returned incorrect - length information for <literal>MEDIUM</literal> and - <literal>LONG</literal> <literal>TEXT</literal> and + <literal>mysql_fetch_fields()</literal> returned incorrect + length information for <literal>MEDIUM</literal> and + <literal>LONG</literal> <literal>TEXT</literal> and <literal>BLOB</literal> columns. (Bug #9735) </para> </listitem> - + <listitem> <para> - <literal>mysqlbinlog</literal> was failing the test suite - on Windows due to <literal>BOOL</literal> being incorrectly + <literal>mysqlbinlog</literal> was failing the test suite on + Windows due to <literal>BOOL</literal> being incorrectly cast to <literal>INT</literal>. (Bug #11567) </para> </listitem> - + <listitem> <para> - <literal>NDBCLuster</literal>: Server left core files + <literal>NDBCLuster</literal>: Server left core files following shutdown if data nodes had failed. (Bug #11516) </para> </listitem> @@ -445,8 +443,8 @@ <para> Server had access denied errors for default accounts on machines where 127.0.0.1 != 'localhost'. (Bug #11822) - </para> - </listitem> + </para> + </listitem> <listitem> <para> @@ -4437,9 +4435,10 @@ <listitem> <para> - InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, - single table <literal>UPDATE…SELECT</literal> and single - table <literal>DELETE…SELECT</literal> clauses when + InnoDB: Relaxed locking in + <literal>INSERT…SELECT</literal>, single table + <literal>UPDATE…SELECT</literal> and single table + <literal>DELETE…SELECT</literal> clauses when <literal>innodb_locks_unsafe_for_binlog</literal> is used and isolation level of the transaction is not serializable. <literal>InnoDB</literal> uses consistent read in these @@ -6836,13 +6835,13 @@ </para> <itemizedlist> - + <listitem> <para> - <literal>MySQL Cluster</literal>: A new + <literal>MySQL Cluster</literal>: A new <literal>-p</literal> option is available for use with the - <command>ndb_mgmd</command> client. When called with this - option, <command>ndb_mgmd</command> prints all configuration + <command>ndb_mgmd</command> client. When called with this + option, <command>ndb_mgmd</command> prints all configuration data to <literal>stdout</literal>, then exits. </para> </listitem> @@ -6857,28 +6856,28 @@ describe the issue that was fixed. Use past tense. --> <itemizedlist> - + <listitem> <para> - The C API function - <literal>mysql_statement_reset()</literal> did not clear + The C API function + <literal>mysql_statement_reset()</literal> did not clear error information. (Bug #11183) </para> </listitem> - + <listitem> <para> - Multiple-table <literal>UPDATE</literal> queries using - <literal>CONVERT_TZ()</literal> would fail with an error. + Multiple-table <literal>UPDATE</literal> queries using + <literal>CONVERT_TZ()</literal> would fail with an error. (Bug #9979) </para> </listitem> - + <listitem> <para> - <literal>mysql_fetch_fields()</literal> returned incorrect - length information for <literal>MEDIUM</literal> and - <literal>LONG</literal> <literal>TEXT</literal> and + <literal>mysql_fetch_fields()</literal> returned incorrect + length information for <literal>MEDIUM</literal> and + <literal>LONG</literal> <literal>TEXT</literal> and <literal>BLOB</literal> columns. (Bug #9735) </para> </listitem> @@ -7122,10 +7121,10 @@ describe the issue that was fixed. Use past tense. --> <itemizedlist> - + <listitem> <para> - When used within a subquery, <literal>SUBSTRING()</literal> + When used within a subquery, <literal>SUBSTRING()</literal> returned an empty string. (Bug #10269) </para> </listitem> @@ -7970,10 +7969,11 @@ and isolation level of the transaction is not set to serializable then <literal>InnoDB</literal> uses a consistent read for select in clauses like <literal>INSERT - INTO…SELECT</literal> and <literal>UPDATE…(SELECT)</literal> - that do not specify <literal>FOR UPDATE</literal> or - <literal>IN SHARE MODE</literal>. Thus no locks are set to - rows read from selected table. + INTO…SELECT</literal> and + <literal>UPDATE…(SELECT)</literal> that do not specify + <literal>FOR UPDATE</literal> or <literal>IN SHARE + MODE</literal>. Thus no locks are set to rows read from + selected table. </para> </listitem> @@ -9774,9 +9774,10 @@ <listitem> <para> - InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, - single table <literal>UPDATE…SELECT</literal> and single - table <literal>DELETE…SELECT</literal> clauses when + InnoDB: Relaxed locking in + <literal>INSERT…SELECT</literal>, single table + <literal>UPDATE…SELECT</literal> and single table + <literal>DELETE…SELECT</literal> clauses when <literal>innodb_locks_unsafe_for_binlog</literal> is used and isolation level of the transaction is not serializable. <literal>InnoDB</literal> uses consistent read in these @@ -33448,9 +33449,9 @@ <para> Changed <literal>LIKE</literal> character comparison to behave as <literal>=</literal>; This means that <literal>'e' - LIKE 'é'</literal> is now true. (If the line doesn't display - correctly, the latter 'e' is a French 'e' with an acute - accent above.) + LIKE 'é'</literal> is now true. (If the line doesn't + display correctly, the latter 'e' is a French 'e' with an + acute accent above.) </para> </listitem>
| Thread | ||
|---|---|---|
| • bk commit - mysqldoc@docsrva tree (paul:1.3105) | paul | 22 Jul |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.659 sec. using MySQL 5.1.14-beta-log